Comment by parliament32
3 months ago
The NPM team has repeatedly commented that it's "too hard", effectively, and would discourage new developers from publishing packages. See:
https://github.com/npm/cli/commit/5a3b345d6d5d175ea9ec967364...
3 months ago
The NPM team has repeatedly commented that it's "too hard", effectively, and would discourage new developers from publishing packages. See:
https://github.com/npm/cli/commit/5a3b345d6d5d175ea9ec967364...
I don't think I'd trust a package from a new developer like that, so this helps filter out people that don't know how to properly maintain a package. If they really want to make onboarding easier, saying "after e.g. 1000 monthly downloads, you'll need to sign your artifacts" is also a viable solution in my opinion.
The npm team is, frankly, a bunch of idiots for saying that. It has been obvious for TEN YEARS that the bar for publishing npm packages is far too low. That’s what made npm what it is, but it’s no longer needed. They should put on their big boy pants.
> discourage new developers from publishing packages
Good.
It's not like these packages are super sophisticated million LOCs masterpieces. ansi-regex is literally just this:
592 bytes of code including comments and whitespace versus which amount of overhead in package description, tarball caches, etc...?
No kidding. New developers need to learn the important skill of doing something correctly, not just “ship fast; break things”