Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with firebase-hosting example #8897

Closed
julianbenegas opened this issue Sep 28, 2019 · 3 comments
Closed

Problem with firebase-hosting example #8897

julianbenegas opened this issue Sep 28, 2019 · 3 comments

Comments

@julianbenegas
Copy link
Contributor

I started from this example. Changed nothing more than what is explained in there to get up and running.

npm run dev works perfectly.
npm run serve (firebase local) throws me the following:

Error: > Couldn't find a pages directory. Please create one under the project root
at Object.findPagesDir (/Users/julianbenegas/Documents/Work/mayeutica-platform-2.nosync/dist/functions/node_modules/next/dist/lib/find-pages-dir.js:3:170)
at new Server (/Users/julianbenegas/Documents/Work/mayeutica-platform-2.nosync/dist/functions/node_modules/next/dist/next-server/server/next-server.js:40:42)
at createServer (/Users/julianbenegas/Documents/Work/mayeutica-platform-2.nosync/dist/functions/node_modules/next/dist/server/next.js:2:133)
at Object. (/Users/julianbenegas/Documents/Work/mayeutica-platform-2.nosync/dist/functions/index.js:10:11)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:692:17)
⚠ Your function was killed because it raised an unhandled error.

Cheers!
@jthegedus

@matchatype
Copy link

Duplicate #8893

@timneutkens
Copy link
Member

Will close this in favor of #8893

@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants