Live data from Hacker News

Upcoming breaking changes for npm v12

github.blog

181–190 of 221 posts

Re: Upcoming breaking changes for npm v12

#181

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]

Or maybe just add a script in package.json to run whatever patch-package does (eg, "install:patch": "npm install && patch-package") instead of whitelisting every package to have that power.

Re: Upcoming breaking changes for npm v12

#183

Earlier 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?

Enemies of democracy don't want to do this because it would require acknowledge that technology companies in the US have been mostly a force of evil rather than good and the idea we should change that makes a small minority of people uncomfortable.

Re: Upcoming breaking changes for npm v12

#184
post #149

I 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

I feel like Bun is even faster than yarn, but I'm afraid to keep using Bun since they made AI rewrite it completely in another language

Re: Upcoming breaking changes for npm v12

#185
post #157

Earlier 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.

Yeah, it's like people are forgetting that the executive team at GitHub was composed of sex pests and people defending said sex pest. Of course they'll call any attempt at unionizing as "damaging" to the company and must be blamed accordingly!

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

#186

I'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.

Strategical positioning for enshittification, control and future squeezing of profits. Embrace, Extend, Extinguish.

https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

Re: Upcoming breaking changes for npm v12

#187

Earlier 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.

Right, the very public two rounds of layoffs the company did right before being "acquired" had nothing to do with them running out of money.

Re: Upcoming breaking changes for npm v12

#188
post #158

Earlier 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 .

The company raised $10M, did two rounds of layoffs totaling a quarter of the company, and was then acquired not long after. Early stage companies like that don't do layoffs unless it's to extend cash runway, but run wild with whatever unfounded fantasy you have about it all.

Re: Upcoming breaking changes for npm v12

#189
post #68

Earlier 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…

This used to be more common but the pattern these days is to have the binaries split into optionalDependencies which declare their supported CPU etc, one per supported platform. Then npm will install just the matching one (optionalDependencies that require a different platform aren't installed).

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

#190
post #157

Earlier 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.

No one said anything about bankruptcy, you seem to have made that up for your "argument" or whatever this is. The company didn't have a viable business model and was running out of cash. MSFT right-sized the team for the project they wanted it to be, rather than the business model the prior company was trying to be.
Post reply on HN