The engine "node" is incompatible with this module. Expected version ">=16.0.0". Got "14.18.3" (while deploying to vercel)

Question

i was trying to deploy my next.js project to vercel but got the following error.

error datastore-pubsub@2.0.0: The engine "node" is incompatible with this module. Expected version ">=16.0.0". Got "14.18.3"
error Found incompatible module.

I tried deleting yarn.lock file but the same error showed up nonetheless.

go in package.json or yarn.lock remove "engines" :{ "node" : 14.x } — Paiman Rasoli, Feb 20 '22 at 09:03
here's the link to the github repo - https://github.com/xylanreeves/bitverse — Xylan, Feb 20 '22 at 09:22
this is because the datastore-core package. it needs a higher version node see inside your vercel project setting you can specify the node version. — Paiman Rasoli, Feb 20 '22 at 09:27
https://vercel.com/docs/runtimes#official-runtimes/node-js/node-js-version see this link. — Paiman Rasoli, Feb 20 '22 at 09:28
It just shows 14.x and 12.x for now, so I think I have to overwrite it by defining it inside package.json file — Xylan, Feb 20 '22 at 09:35
yes, I checked node version 16 is not available in vercel try to specify it inside package.json. — Paiman Rasoli, Feb 20 '22 at 09:36
It throws another error now: Error: Found invalid Node.js Version: ">= 16.13.2". Please set "engines": { "node": "14.x" } in your `package.json` file to use Node.js — Xylan, Feb 20 '22 at 09:43
I suggest deploying your project to Heroku. because you can customize your node version. — Paiman Rasoli, Feb 20 '22 at 09:45
Just create an account, create a project and connect the project to the GitHub repository. — Paiman Rasoli, Feb 20 '22 at 09:46
I have two options now if I go with vercel, I can try using '--ignore-engines' with yarn or use 14.x version of node in my project. — Xylan, Feb 20 '22 at 09:47
I'll try heroku, but env (using env.local) works different in next.js though, that's what am worried about. — Xylan, Feb 20 '22 at 09:48
no, it is super easy to go just go setting tab => reval config vars — Paiman Rasoli, Feb 20 '22 at 09:50
or if you want let me to deploy your project in my heroku first? — Paiman Rasoli, Feb 20 '22 at 09:51
okay I'll give it a try! but vercel definitely needs to work on this 'node engine anomaly' — Xylan, Feb 20 '22 at 09:52
Nice job, you will definitely find a way for that if you solve it please comment your solution here. — Paiman Rasoli, Feb 20 '22 at 09:54
Let us [continue this discussion in chat](https://chat.stackoverflow.com/rooms/242190/discussion-between-paiman-rasoli-and-xylan). — Paiman Rasoli, Feb 20 '22 at 10:13

score 5 · Answer 1 · answered Mar 02 '22 at 02:57

5

Your dependency is relying on Node.js 16+, but Vercel currently does not have support, as we are dependent on AWS. You can follow along here: https://github.com/vercel/community/discussions/37

Should hopefully be resolved very soon.

answered Mar 02 '22 at 02:57

leerob

2,876
1
18
38

so good to see you here, I follow you on youtube! And yes I read about the AWS thing, deployed the site on netlify for now. thank you and cheers – Xylan Mar 02 '22 at 05:06

The engine "node" is incompatible with this module. Expected version ">=16.0.0". Got "14.18.3" (while deploying to vercel)

1 Answers1