Version 13.7.0 now requires manually adding "runtime" configuration in firebase.json about firebase-tools HOT 5 CLOSED

I think this also applies to nodejs:

I just just upgraded (npm i -g firebase-tools) and started receiving:

functions: Your requested "node" version "20" doesn't match your global version "18". Using node@18 from host.

even though I have node version 18 in package.json

by setting functions: { runtime: "nodejs18" } in firebase.json it stopped giving the warning.

from firebase-tools.

Hey @vitoras, thanks for the thorough report as well as for sharing your observations, and thanks @amfc for the additional information. I was able to reproduce the issue. It looks like both Node.js and Python runtimes are affected here.

As a workaround for those who also encounter this issue, please specify the runtime in your firebase.json file. Here's references for setting the Node.js version and Python version. I’ll raise this to our engineering team so that we can determine what the appropriate action here would be. I’ll also mark this as reproducible.

from firebase-tools.

Today's release of the CLI fixes the issue.

from firebase-tools.

I think this also applies to nodejs:

I just just upgraded (npm i -g firebase-tools) and started receiving:

functions: Your requested "node" version "20" doesn't match your global version "18". Using node@18 from host.

even though I have node version 18 in package.json

by setting functions: { runtime: "nodejs18" } in firebase.json it stopped giving the warning.

Yeah, this idea was raised in this issue, but maybe they overlooked that impact.

from firebase-tools.

Today's release of the CLI fixes the issue.

Thanks a lot, now the emulators are working as before!

from firebase-tools.