Earlier quoted context omitted.
Given that has an impact over the whole industry, I will for sure tell you that patching on install SHOULD NOT be a thing. Up to you to run your own post install script yourself
[flagged]
Upcoming breaking changes for npm v12
181–190 of 221 posts
Re: Upcoming breaking changes for npm v12
#182Re: Upcoming breaking changes for npm v12
#183Earlier quoted context omitted.
Destroy what exactly? And replace with what?
Can y’all just state your opinions on these things rather than constantly asking bait-y questions?
Re: Upcoming breaking changes for npm v12
#184I wonder if there are still reasons to use yarn? Has yarn also implemented safeguards to protect against supply chain attacks? Until now, I only knew about pnpm. It’s great that npm has followed up.
I don't know what NPM is doing, but yarn installs deps much faster than NPM
Re: Upcoming breaking changes for npm v12
#185Earlier quoted context omitted.
https://www.theregister.com/software/2019/04/01/nice-people-... Year before the MSFT takeover. No idea about their actual financials but they were definitely shedding headcount pre 2020, including kicking people for trying to unionise.
Nothing in there suggests that this was done to save the company from bankruptcy, which was the wild claim.
After all the company was in such dire straights that they were acquired for $7.5 billion! Only companies with terrible prospects get acquired, that's just business 102.
Re: Upcoming breaking changes for npm v12
#186I'm not sure how I missed that npm was acquired by GitHub, but man, a lot of stuff suddenly makes a lot of sense. I really can't think of a worse home for such a critical part of the Node ecosystem.
https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
Re: Upcoming breaking changes for npm v12
#187Earlier quoted context omitted.
It's literally a Google search away. If you had the time to write this comment, you had more than enough time to do the search.
Google said you are 100% wrong.
Re: Upcoming breaking changes for npm v12
#188Earlier quoted context omitted.
It's literally a Google search away. If you had the time to write this comment, you had more than enough time to do the search.
Not my job to proof the wild claim that the layoffs were to save the company from bankruptcy .
Re: Upcoming breaking changes for npm v12
#189Earlier quoted context omitted.
Java‘s Maven never had them, never felt a need for them. What is their purpose in JS land?
native modules. nodejs can have native modules (written in C++, Rust, etc...). Projects usually ship prebuilt natives binaries (for each arch/OS/Nodejs ABI combination) hosted on GitHub Releases and download them automatically at installation time; fallback to build from source if not found. that's where scripts are used the reason for not bundling all native binaries is becasue the no. of combinations are huge and i…
The fact that most of the ecosystem has moved to this pattern is a big part of why this change is now feasible.
Re: Upcoming breaking changes for npm v12
#190Earlier quoted context omitted.
https://www.theregister.com/software/2019/04/01/nice-people-... Year before the MSFT takeover. No idea about their actual financials but they were definitely shedding headcount pre 2020, including kicking people for trying to unionise.
Nothing in there suggests that this was done to save the company from bankruptcy, which was the wild claim.