Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Upcoming breaking changes for npm v12

github.blog

Post reply on HN
Print view View original

101–110 of 221 posts

Re: Upcoming breaking changes for npm v12

#101

Post by _pythonlover_ »

shimman wrote: post #29
shagie wrote: post #12

Earlier quoted context omitted.

NPM Is Joining GitHub - https://news.ycombinator.com/item?id=22594549 (March 16, 2020; 571 comments; 1829 points) - https://github.blog/news-insights/company-news/npm-is-joinin... Some of it aged... interesting. Top comment: > Microsoft doesn’t do everything right but the GitHub acquisition has honestly gone better than I ever expected. Rather than forcing GitHub to adopt Microsoft centric policies, Microsoft has ado…

MSFT acquisition of NPM was a massive shit show, they fired many staff engineers and people that were at github for quite a while. Top comment was a liar.

I was part of the npm team at GitHub. They laid off almost the entire team to focus on AI (CTO literally told us on the layoff announcement call that they're doing this to focus on Copilot)

Re: Upcoming breaking changes for npm v12

#102

Post by behindsight »

mort96 wrote: post #99
behindsight wrote: post #39

Earlier quoted context omitted.

> Retired? What does that even mean in this context "retired" is probably a followup to functionality that was "deprecated". I agree "breaking" would be clearer

What exactly is it that's now retired that used to be deprecated? Isn't this just a collection of breaking changes to defaults?

if you go to the full changelog on the blog and click on the "retired" button, the url will have type=deprecations as the parameter.

It's a holdover from previous posts where there were more clearly defined deprecations.

but yes, in this case it's more of a behavioural change of defaults, so they just picked the closest vaguely mapped retired/deprecations tag.

1: https://github.blog/changelog/?type=deprecations

Re: Upcoming breaking changes for npm v12

#103

Post by pjmlp »

ok_dad wrote: post #56
w29UiIm2Xz wrote: post #24

Earlier quoted context omitted.

To be fair, the vibes (at the time) were that Microsoft has changed. Probably, in some way, a zero-interest rate phenomena.

Young people thought M$ was changing, the old folks knew it was just another cycle of embrace, extend, extinguish.

Old folks are also aware that applies to every single big tech company that actually sponsors the FOSS tools many don't want to pay anything back, while expecting to be paid themselves.

Old folks also remember the days when it was possible to make a living out of selling software tools.

Re: Upcoming breaking changes for npm v12

#104

Post by jamiem »

alexghr wrote: post #94

Are the current LTS node versions (iirc 22, 24, 26) going to update the bundled npm to v12 to benefit from these security fixes? All come with npm v11 now

Major npm version bumps have landed mid-stream for node in the past: v18.19.0[1] and v20.10.0[2] bumped npm 9 to 10.

[1]: https://nodejs.org/en/blog/release/v18.19.0#npm-updated-to-v... [2]: https://nodejs.org/en/blog/release/v20.10.0

Re: Upcoming breaking changes for npm v12

#106

Post by 7bit »

tomnipotent wrote: post #58
shimman wrote: post #29

Earlier quoted context omitted.

MSFT acquisition of NPM was a massive shit show, they fired many staff engineers and people that were at github for quite a while. Top comment was a liar.

> they fired many staff engineers Would you rather the company went under after it ran out of money and had to fire everyone instead? Not to mention a quarter of the company was laid off the year before the acquisition.

Was that the case? Can you provide sources to your claims and provide a foundation to your theories?

Re: Upcoming breaking changes for npm v12

#108

Post by hnfong »

ok_dad wrote: post #56
w29UiIm2Xz wrote: post #24

Earlier quoted context omitted.

To be fair, the vibes (at the time) were that Microsoft has changed. Probably, in some way, a zero-interest rate phenomena.

Young people thought M$ was changing, the old folks knew it was just another cycle of embrace, extend, extinguish.

The ruthlessness of the Microsoft that we remember was probably due to influence from Bill Gates.

He is famous for hyper-competitiveness and strong desire to win at all costs.

Re: Upcoming breaking changes for npm v12

#109

Post by Forgeties79 »

ok_dad wrote: post #56
w29UiIm2Xz wrote: post #24

Earlier quoted context omitted.

To be fair, the vibes (at the time) were that Microsoft has changed. Probably, in some way, a zero-interest rate phenomena.

Young people thought M$ was changing, the old folks knew it was just another cycle of embrace, extend, extinguish.

Remember when folks thought Phil Spencer was gonna right the Xbox ship lol

Re: Upcoming breaking changes for npm v12

#110

Post by b112 »

alexghr wrote: post #94

Are the current LTS node versions (iirc 22, 24, 26) going to update the bundled npm to v12 to benefit from these security fixes? All come with npm v11 now

They are changes in defaults, which could be construed as a security posture change, but the security fix is in everyone's hands. Just set proper defaults, as per article, and done.

I think the best part of this change, is that the default change will mean that lots of new DEVs just running an install, will see instant breakage with annoying packages that presume these settings are on. It should force people to stop expecting scripts to be runnable, for example.

Post reply on HN