Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node v14.16.1 is not compatible anymore (we now need node v14.17.0) #110

Open
gogo9th opened this issue Aug 9, 2023 · 1 comment
Open

Comments

@gogo9th
Copy link

gogo9th commented Aug 9, 2023

npm ERR! code ENOTSUP
npm ERR! notsup Unsupported engine for [email protected]: wanted: {"node":"^14.17.0 || ^16.13.0 || >=18.0.0"} (current: {"node":"14.16.1","npm":"6.14.12"})
npm ERR! notsup Not compatible with your version of node/npm: [email protected]
npm ERR! notsup Not compatible with your version of node/npm: [email protected]
npm ERR! notsup Required: {"node":"^14.17.0 || ^16.13.0 || >=18.0.0"}
npm ERR! notsup Actual:   {"npm":"6.14.12","node":"14.16.1"}

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/skyer/.npm/_logs/2023-08-09T05_50_11_397Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: `./scripts/postinstall`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/skyer/.npm/_logs/2023-08-09T05_50_11_435Z-debug.log
@jawline
Copy link
Member

jawline commented Oct 2, 2023

I think 14.16.1 is still correct with the adjusted instructions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants