JoshBent

8y

I don't remember/saw if somebody posted it in this much detail, but here's how one developer essentially showed how broken npm once again is, by just removing all his published packages, basically breaking thousands of other packages that depended on it, very interesting read, especially to understand how npm can't be relied on.

https://theregister.co.uk/2016/03/...

http://blog.npmjs.org/post/...

https://medium.com/@mproberts/...

https://arstechnica.com/information...

undefined

npm

Ranter

Comments

3

D--M

2218

8y

Your alternative is to right the code yourself.

Relying on it is fine. What I don't understand is why people used a fucking package for 11 lines of code.

Seriously, they deserve to have their shit broken.
0

D--M

2218

8y

@amahlaka
I should of clarified what I meant, I was more speaking of the users who actually did npm install left-pad
2

Forside

1434

8y

How can one be so lazy as to look for a package that provides such a simple function? It's like a matter of a minute or less to code it, probably faster than finding that package.

And beyond that, why does someone even publish such a package??
0

d4ng3r0u5

4528

8y

11 lines of code? fuck their package.json is probably longer than that

Related Rants

devRant © 2021 Hexical Labs LLC
Privacy Policy | Terms of Service