Upcoming breaking changes for npm v12
github.blog
Upcoming breaking changes for npm v12
1–10 of 221 posts
Re: Upcoming breaking changes for npm v12
#2didn't know npm was owned by github..
well, that explains things...
Re: Upcoming breaking changes for npm v12
#3didn't know npm was owned by github.. well, that explains things...
Most people know this but the _real_ reason it explains things is that GitHub is owned by Microsoft. Oh, and Microsoft moved GitHub to Azure
Re: Upcoming breaking changes for npm v12
#4I hope GitHub changes their vibecoded badges, what does RETIRED even signify in this context? Why does the preview have to be in ominous red?
Re: Upcoming breaking changes for npm v12
#5Looks good? But doesn't this just change the compromise window from first installation to first run?
Re: Upcoming breaking changes for npm v12
#6Looks good? But doesn't this just change the compromise window from first installation to first run?
Better than nothing. That’s the same problem every package manager has.
Re: Upcoming breaking changes for npm v12
#7I hope GitHub changes their vibecoded badges, what does RETIRED even signify in this context? Why does the preview have to be in ominous red?
Hahaha that's amazing, just a big red "RETIRED" badge above their blog post? What the hell
Re: Upcoming breaking changes for npm v12
#8They should have added a 1-day age limit by default, so security scanners have some time.
Re: Upcoming breaking changes for npm v12
#9this release fixes a vulnerability reported 10 years ago
Re: Upcoming breaking changes for npm v12
#10didn't know npm was owned by github.. well, that explains things...
yes, since 2020