Supported node/npm versions #5

Which version of node and/or npm should I support in my app or library

At Nextcloud, we use the current active LTS versions of Node and NPM.
You can check the schedule in https://endoflife.date/nodejs
The Node version is only used during development time, so using the latest active LTS version allows developers to use new versions of tools while still keep the update cycle down at once a year.

How to comply

1. Make sure to have your engines section up-to-date in your package.json as we have scripts to update them once a version become unmaintained.

   You can specify the version of node that your stuff works on
   You can also use the "engines" field to specify which versions of npm are capable of properly installing your program. For example:

   {
     "engines": {
       "node": "^24.0.0",
       "npm": "^11.3.0"
     }
   }

2. Please also use appropriates workflows like you can find in our templates repository since they use the engines block to properly setup node and npm
3. Engines expose the minimum version we support. As a dev, you are free to use newer releases, but testing and releases must be done against those versions.
   Warnings might be thrown in the console, but they will not impact the process.
4. We recommend devs to use NVM to quickly switch between versions

Schedule

Changelog

• 2022-06-30 - First draft of this standard. Moving from Node14 to Node 16 exceptionally because node 14 ships npm6 by default
• 2024-01-15 - Updated all nodes versions to 20 and npm to 10
• 2025-01-14 - Switch to the current LTS version, as of today Node 22.
• 2025-11-01 - Updated all nodes versions to 24 and npm to 11