Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou...
by ajdude on Sunday January 09, 2022 @11:48PM
(#29870790)
This whole situation reminds me of that post a little while ago
> I will pay you cash to delete your npm module
Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou...
by a3w on Monday January 10, 2022 @12:36PM
(#29878374)
So finally F.L.O.S. Software pays out. Shame that the dev did not apply for some compensation. All in all, not very rational of him.
Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou...
by tomjen3 on Monday January 10, 2022 @01:06AM
(#29871220)
Keeping dependencies loosely coupled and reusable has been best practice since forever, but it is only really with NPM that it has become the default.
Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou...
by chrisandchris on Monday January 10, 2022 @06:47AM
(#29873343)
But actually it's more like dependency hell because you pull in the same dependency in N versions and you can't update transitive dependencies in a senseful matter? And you get a lot of libraries that are like 4 lines and computing basic operations (like there was a lib "isOdd"... i mean x% 2 === 0?).
So you won't gain anything from this type of dependency management, because it is way to complicate to understand and to manage for a developer.
Last I checked create-react-app pulls around 1k transitive dependencies. Can't really blame JS for that, can we?