firebase-gcp-examples: Error in deploy

Hi all, please see my new example which addressed many of the issues people had with the setup. I believe the structure will cause less confusion.

https://github.com/jthegedus/firebase-gcp-examples/tree/master/functions-nextjs

I intend to update this example using the new emulator within the next 48 hours

Lol, sorry about that.

I have the new emulator in this example, though the Next.js development server doesn’t run well on the local Cloud Function. I don’t think you will need to run the local emulator though as the next dev server does most of what you need. The Cloud Function server is just a bridge between the two envs, not a fully working development setup.

Given the drastically new example I will close this. If you find issues with the new setup please do raise new issues! Thanks

@robsonkades I changed

"deploy": "yarn firebase deploy --only functions,hosting"

to

"deploy": "NODE_ENV=production yarn firebase deploy --only functions,hosting"

and it worked

Is this repo public and could you share it? Would make debugging easier.

I’ve just gone back to using npm as everyone has it whereas that is not the case for yarn unfortunately.

I’ve got a completely reworked version of this which I will release this weekend. It simplifies the setup much more and leverages the latest Next.js features. Stay tuned.

Hi @robsonkades firebase serve is problematic. I wouldn’t recommend using it. See my recommendations on the next.js repo example. I intend to update this example using the new emulator within the next 48 hours.

Thanks for taking the time to report this here 💯

I got it to work with more banging my head against the package.json, I think it was a mistake to run npm run dev within the src/client folder to get a local version of it up and running. I migrated the package.json over to using npm and installed cross-env as well as install-peers to get past some of the errors I was seeing on build.

Google recently updated Cloud Functions to be private by default, so you are required to configure the IAM permissions on a per function level to allow access. I am planning an entire rewrite of my next.js guide in the coming weeks to address all these issues and more. Thanks for sharing your results here.

Alternative to @rscotten’s comment with NPM.

"scripts": {
    "setup": "firebase use --add",
    "build:client": "next build src/client",
    "build:server": "babel src/server --out-dir dist/server --source-maps",
    "build": "npm run build:client && npm run build:server",
    "watch:client": "next src/client",
    "watch:server": "babel src/server --out-dir dist/server --source-maps --watch",
    "watch": "npm run watch:client & npm run watch:server",
    "serve": "cross-env NODE_ENV=production firebase serve --only functions,hosting",
    "predeploy": "rimraf dist/ && npm run build",
    "deploy": "cross-env NODE_ENV=production firebase deploy --only functions,hosting"
  }