Why aren't Node.js package managers interoperable?

1. react-mapbox-gl

   1 3 1,935 0.0 TypeScript

   A React binding of mapbox-gl-js

   This is a real concern. I've worked on some Yarn projects where I sometimes forget and accidentally run npm. Although these package managers (I'll call them PMs for short) are interoperable to some degree, there are important differences between these tools, so you should know what you're getting into. Even in seemingly simple projects, results can vary. Here are two reports of things working with one PM, but not another. Moreso, running install once is very different from continuous concurrent use, where you're adding and removing packages and more.

2. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. docz

   2 18 23,682 0.0 TypeScript

   ✍ It has never been so easy to document your things!

   

   This is a real concern. I've worked on some Yarn projects where I sometimes forget and accidentally run npm. Although these package managers (I'll call them PMs for short) are interoperable to some degree, there are important differences between these tools, so you should know what you're getting into. Even in seemingly simple projects, results can vary. Here are two reports of things working with one PM, but not another. Moreso, running install once is very different from continuous concurrent use, where you're adding and removing packages and more.

4. patch-package

   3 66 10,575 1.0 TypeScript

   Fix broken node modules instantly 🏃🏽‍♀️💨

   

   Yarn 2+ and pnpm support patching dependencies with your custom code. For npm and Yarn 1, you can use a library, but remember to somehow ignore it when using other PMs.

5. yarn

   4 35 41,482 3.0 JavaScript

   The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry

   

   Upgrading dependencies: Yarn 1's yarn upgradeonly upgrades direct dependencies of the current workspace. Yarn 2's up ignores the version ranges in your package.json and upgrades for all workspaces. npm's and pnpm'supdate respect your version ranges and upgrade indirect dependencies as well.

6. cli

   5 79 8,628 9.7 JavaScript

   the package manager for JavaScript (by npm)

   

   Using npm on a project with a yarn.lockwill update the yarn.lock file alongside the package-lock.json: "In npm v7, if a yarn.lock file exists, npm will use the metadata it contains[...]. If packages are added or removed, then the yarn.lock file will be updated." I was pleasantly surprised to find out that this worked (minus a few bugs). Running npm remove x removed it from package.json, package-lock.json, and yarn.lock. Even more impressive, removing/adding packages by manually editing package.json, then running npm i also updated the Yarn lockfile. Well done, npm team.

7. rfcs

   6 35 736 5.6 JavaScript

   Public change requests/proposals & ideation (by npm)

   

   npm also plans to support pnpm-style node_modules

Suggest a related project