4 ms·
>resolved by dropping npm-cli from the official releases. But that would break 7 years of documentation and tutorials, likely bad for newcomers and thus the ec
by cheapsteak 9y ago
>resolved by dropping npm-cli from the official releases.
But that would break 7 years of documentation and tutorials, likely bad for newcomers and thus the ecosystem
- josteink 9y agoNot to mention quite a few CI build pipelines.
- pluma 9y agoFWIW it's trivial to install yarn already: https://yarnpkg.com/en/docs/install https://yarnpkg.com/en/docs/install NPM currently doesn't provide a standalone distribution as far as I can tell, but presumably they would offer one if they no longer had the luxury of being bundled with Node. Since changes generally don't happen overnight I would expect a transitional period where Node still bundles npm-cli but npm Inc has the time to prepare a standalone distribution before yarn replaces npm-cli. Additionally downstream channels could decide to provide legacy packages containing both.
- k__ 9y agoso npm has created a huge vendor lock-in and we should live with it?!
- cheapsteak 9y agoAs with any vendor lock-in situation, decisions should be made based on cost/benefit Perhaps you can help come up with a strategy that gracefully handles breakages and eventually results in dropping npm-cli
- SilasX 9y ago"The only reason God could create the world in six days is, He didn't have to worry about backward compatibility."
- fibo 9y agoLOL