News for hackers. Stuff that matters.

A comment on Upcoming breaking changes for NPM v12. Parent comment

Re:Upcoming breaking changes for NPM v12 by behindsight on Tuesday June 09, 2026 @07:52PM (#48469416)
> 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

[ Parent | on HN ]
Re:Upcoming breaking changes for NPM v12 by mort96 on Wednesday June 10, 2026 @01:48AM (#48471952)
What exactly is it that's now retired that used to be deprecated? Isn't this just a collection of breaking changes to defaults?
[ Parent | on HN ]
Re:Upcoming breaking changes for NPM v12 by behindsight on Wednesday June 10, 2026 @01:56AM (#48472011)
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

[ Parent | on HN ]