Firebase

325 views
Skip to first unread message

Ashim Ghimire

unread,
Oct 9, 2023, 1:57:18 PM10/9/23
to Firebase Google Group
Building a Cloud Function to run this application. This is needed due to:
 • middleware
 • non-static route /api/auth/[...nextauth]
 • non-static route /api/config
 • non-static route /api/hello
 • non-static route /api/login
 • and 64 other reasons, use --debug to see more

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'ehr-front...@0.1.0',
npm WARN EBADENGINE   required: { node: '18' },
npm WARN EBADENGINE   current: { node: 'v16.16.0', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'n...@10.2.0',
npm WARN EBADENGINE   required: { node: '^18.17.0 || >=20.5.0' },
npm WARN EBADENGINE   current: { node: 'v16.16.0', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN deprecated query...@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm ERR! code 2
npm ERR! path /home/pooja/Documents/asim/nextapp/.firebase/fir-authentication-300411/functions/node_modules/yarn
npm ERR! command failed
npm ERR! command /home/pooja/.cache/firebase/runtime/shell -c -- :; (node ./preinstall.js > /dev/null 2>&1 || true)
npm ERR! /bin/sh: 0: Illegal option --

Is there v18.17.1 available for deploying firebase for next js application

Peter Lokidor

unread,
Oct 9, 2023, 4:34:06 PM10/9/23
to fireba...@googlegroups.com
--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/77f6b518-a774-4121-a845-6052721c70b6n%40googlegroups.com.

jamesd...@google.com

unread,
Oct 9, 2023, 8:12:24 PM10/9/23
to Firebase Google Group
Node 18 is a valid engine for the Firebase NextJS integration, it will however chose the version of Node that you're running locally. Can you double check that you're running `firebase deploy` from a Node 18 context?

If you're still running into an issue, please open an issue on firebase/firebase-tools

Reply all
Reply to author
Forward
0 new messages