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.js 14 is no longer supported #1583

Closed
jeanpierrecarvalho opened this issue Aug 15, 2023 · 4 comments · Fixed by #1585
Closed

Node.js 14 is no longer supported #1583

jeanpierrecarvalho opened this issue Aug 15, 2023 · 4 comments · Fixed by #1585

Comments

@jeanpierrecarvalho
Copy link

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

  • Ensure the package.json file of the project specifies that it can use Node.js versions 14.16.0 or 16.11.0.
  • Install the required dependencies using pnpm: pnpm install
  • Observe the error message that is generated.

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 version 14.16.0 or Node.js version 16.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

@jeanpierrecarvalho
Copy link
Author

image

@pi0 pi0 changed the title Incompatibility error with engines in package.json and pnpm version Node.js 14 is no longer supported Aug 15, 2023
@pi0
Copy link
Member

pi0 commented Aug 15, 2023

The packagemanager field in the repository is for local development (of repo) not meant for end-users.

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.

@Hebilicious
Copy link
Contributor

@pi0 Note that maintenance for node16 also drops in 1month https://endoflife.date/nodejs

@pi0
Copy link
Member

pi0 commented Aug 16, 2023

@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.

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

Successfully merging a pull request may close this issue.

3 participants