Unsupported engine
See original GitHub issueDescription 🐜
I am getting the logs below when installing next-auth ^4.1.2 on next 12.0.8.
Is this a bug in your own project?
Yes
How to reproduce ☕️
run npm install next-auth@latest
Screenshots / Logs 📽
npm i next-auth@latestnpm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'next-auth@4.1.2',
npm WARN EBADENGINE required: { node: '^12.19.0 || ^14.15.0 || ^16.13.0' },
npm WARN EBADENGINE current: { node: 'v17.3.1', npm: '8.3.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'openid-client@5.1.2',
npm WARN EBADENGINE required: { node: '^12.19.0 || ^14.15.0 || ^16.13.0' },
npm WARN EBADENGINE current: { node: 'v17.3.1', npm: '8.3.0' }
npm WARN EBADENGINE }
Environment 🖥
System: OS: macOS 12.1 CPU: (8) arm64 Apple M1 Memory: 373.56 MB / 16.00 GB Shell: 5.8 - /bin/zsh Binaries: Node: 17.3.1 - /opt/homebrew/bin/node Yarn: 1.22.17 - /opt/homebrew/bin/yarn npm: 8.3.0 - /opt/homebrew/bin/npm Browsers: Chrome: 97.0.4692.99 Safari: 15.2 npmPackages: next: 12.0.8 => 12.0.8 next-auth: ^4.1.2 => 4.1.2 react: 17.0.2 => 17.0.2
Contributing 🙌🏽
No, I am afraid I cannot help regarding this
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Unsupported engine node / NPM only when building in Docker
The engines property in the package.json allows us to establish a range of versions. With >=12 is asking for a node with version...
Read more >npm install failure because Unsupported engine it asset ...
Description I got a Macbook Pro with M1 Chip. the first versión available for this arch is 15.0. I'm trying to run a...
Read more >How to prevent npm install for unsupported Node.js versions
The engines property. The engines property in the package.json can be used to define supported Node.js versions. It can accept a version range....
Read more >Prevent npm install for not supported Node.js versions
Use a local npm configuration to prevent users from installing your module/project with an unsupported Node.js version.
Read more >The package-lock.json file was created with an old version of ...
0' } } 13:37:27 npm WARN EBADENGINE Unsupported engine { package: '@wdio/dot-reporter@7.4.2', 13:37:27 npm WARN EBADENGINE required: { node: '>=12.0.0' }, 13:37 ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

This has also been asked multiple times. Before opening a new issue, I highly recommend doing a search in old issues/discussions. For first contributors, see this video on how to help maintainers: https://www.youtube.com/watch?v=cuoNzXFLitc
https://github.com/nextauthjs/next-auth/issues/3715#issuecomment-1020147118
The answer is more nuanced than that. Technically everything works, and you are safe to ignore the warning. Node 17 is not an LTS release and one of our dependencies only aims to support those.
It runs rigorous tests against all active releases of Node.js to make sure that those all work.