-
Notifications
You must be signed in to change notification settings - Fork 509
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.js 14 is no longer supported #1583
Comments
The The engine field is for users that install the nitro package. It seems Nitro no longer works with Node.js 18 since we use some new APIs of Node.js 16 and 14 is EOL. /cc @danielroe We might consider doing same for Nuxt as well and drop 14. |
@pi0 Note that maintenance for node16 also drops in 1month https://endoflife.date/nodejs |
@Hebilicious Our take is to not "break" installations unless have to (and nitro CI is passing with Node.js 16 ATM). Although we will start with soft runtime warnings about stopping to use of Node.js 16 because of EOL and possible security. |
Environment
Nitro Package Version: 2.5.2
Node Version: v14.16.0, v16.11.0
Package Manager: pnpm@8.6.12
Operating System: Linux
Reproduction
Describe the bug
I encountered a compatibility issue with the Nitro package and the pnpm package manager version
8.6.12
. The package.json file of the project indicates that it can use either Node.js version14.16.0
or Node.js version16.11.0
.However, when attempting to install the dependencies using
pnpm (pnpm install)
, the following error is thrown:ERROR: This version of pnpm requires at least Node.js v16.14 The current version of Node.js is v14.16.0 Visit https://r.pnpm.io/comp to see the list of past pnpm versions with respective Node.js version support.
It seems that there is an inconsistency between the allowed Node.js versions in the package.json file and the requirement imposed by the pnpm package manager version
8.6.12
. The error message indicates that the current version of Node.js (v14.16.0) falls below the required version (v16.14) for the specified pnpm version.Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: