Comment on When "Everything" Becomes Too Much: The npm Package Chaos of 2024 - Socket
dependencyinjection@discuss.tchncs.de 10 months agoIf used in larger systems it can be a pain to maintain code bases as you could install an innocuous package but that package may depend on 100 other packages which in turn could have other dependencies and it cascades.
This can introduce bugs into your code which can be a pain to resolve.
FrameXX@discuss.tchncs.de 10 months ago
Isn’t this a problem with every package/library system? Is there really a solution to this that doesn’t limit packages on their dependencies?
dependencyinjection@discuss.tchncs.de 10 months ago
Thats a good question and I’m not sure to be honest.
We use NPM at work client side for React Typescript and Nuget server side for C# .net and all I know is the senior always complains about NPM but not NuGet I do believe the backend is less package reliant on our applications so maybe that’s why it’s not as bad.