Comments (5)
Node.js v16 support dropped. Use at least Node.js v18.12.
Lockfile version bumped to v7.
Support for lockfile v5 is dropped. Use pnpm v8 to convert lockfile v5 to lockfile v6
What is it with you guys just dropping support for things and skipping node versions? Why? You do realise this affects people right? Not just development environments but build agents as well.
I'm pretty sure backwards compatibility can be managed better? At least put a note in the release notes on why support for a version is dropped...
(PS I don't mean for this comment/issue to come off as overly critical - I love what you guys do and appreciate it - but a simple upgrade should not break everything)
from pnpm.
Node.js 17 is not an LTS version, when Node.js 18 came out it stopped receiving updates, so don't expect long term support for non-lts versions.
It does affect people, hence it is done in a breaking upgrade.
You can use the standalone version of pnpm that is bundled to an executable. In that case you don't care about which node.js version is on the system. Instruction are here: https://pnpm.io/installation#using-a-standalone-script
from pnpm.
Maybe we want to clarify the change log so it says
Node.js v16 and v17 support dropped?
from pnpm.
What is it with you guys just dropping support for things and skipping node versions? Why? You do realise this affects people right? Not just development environments but build agents as well.
I'm pretty sure backwards compatibility can be managed better? At least put a note in the release notes on why support for a version is dropped...
@mika76 pnpm is actually very strict about following semver requirements. Node versions get dropped only for major version updates of pnpm (same like it is a common practice for other popular projects). The whole point of major version releases is to raise awareness to the fact that there can be changes which are not backwards compatible. If you blindly upgrade your dependencies to a new major version, you should be clear about the implications of that.
You can see the current release schedule on e.g. https://nodejs.org/en/about/previous-releases, which will tell you that Node v18 and lower are already in maintenance mode, and Node v20 is the active LTS version. "Use at least Node.js v18.12." in a changelog should make it pretty clear for you what is supported still ;)
from pnpm.
My question is why stop supporting them? Just because node doesn't support their old version doesn't mean pnpm would stop working on them, they have been battle tested and would still work without issue.
Or rather my question is not why stop "supporting" but why hard-lock us from running with them. Support could be stopped officially but pnpm will not run at all if using those node versions, which is strange to me. Why not put in a hard lock once a bug is actually found which is affected by that node version. You don't see app's putting in a hard lock on working on Windows 8 because it's "out of support" by Microsoft.
And if there is an actual reason to stop it from running on them, then make it clear somewhere why.
from pnpm.
Related Issues (20)
- Cannot read properties of undefined (reading 'includes') HOT 2
- pnpm workspace incorrectly resolves bin exports with @org/ in package name
- JSDoc @type import doesn't work with indirect dependencies HOT 1
- Automatic installation of a direct dependency's peer dependencies doesn't yield the expected result HOT 5
- pnpm install --silent should display fatal errors HOT 3
- Overrides not supported for deep transitive dependencies
- pnpm self-update not work HOT 2
- PNPX does not respect the given package with version HOT 1
- [email protected] deploy lost the pkgs in node_modules HOT 2
- "bundledDependencies" field is not effected
- Unable to install unpublished packages in the workspace HOT 1
- pnpm 9.9.0 installs different Vite versions in a monorepo HOT 1
- postinstall script cause `file:` protocol not work properly
- Environment variable expansion is not applied array values in `.npmrc`
- Dependency fails to dedupe HOT 6
- pnpm dev with svelte kit breaks if the project folder path in which is being run is too long
- Configuration option to specify packages that should only be resolved once HOT 3
- `manage-package-manager-versions`: machine hangs for several minutes and then prints error HOT 2
- `bin` file of peer-dependency is not copied over to workspace root project `node_modules` folder
- `pnpm patch` folder not cmd/ctrl-clickable in VS Code HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pnpm.