CODEWITHSUNDEEP
node.jsfirebasefirebase-cli
Doug Stevenson
Doug Stevenson

Reputation: 317467

Update of Firebase CLI to 8.4.0 gives errors about "Unsupported engine" saying '{"node":">=10"}'

After upgrading to 8.4.0 with npm i -g firebase-tools, the following is shown:

npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=10"} (current: {"node":"8.16.2","npm":"6.14.5"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=10"} (current: {"node":"8.16.2","npm":"6.14.5"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=10"} (current: {"node":"8.16.2","npm":"6.14.5"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=10"} (current: {"node":"8.16.2","npm":"6.14.5"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=10"} (current: {"node":"8.16.2","npm":"6.14.5"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]

What should I do to resolve this?

Upvotes: 4

Views: 3463

Answers (1)

Doug Stevenson
Doug Stevenson

Reputation: 317467

With the release of Firebase CLI 8.4.0, it appears a lot has changed, including a new local emulator UI. Among the changes are some modules that now require a minimum node version of 10. That's what the error messages are saying with:

Unsupported engine for module@version: wanted: {"node":">=10"}

If your local node version is less than 10, you will see these errors. It's time to upgrade your node version. If you're using nvm, that's as simple as typing nvm install 10. This does not affect the version of node targeted by Cloud Functions at the time of deployment. The version of node for deployment is still declared in your package.json.

Upvotes: 1

Related Questions