Programming

17398 readers

96 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

128

When "Everything" Becomes Too Much: The npm Package Chaos of 2024 (socket.dev)

submitted 9 months ago* (last edited 9 months ago) by testeronious@lemmy.world to c/programming@programming.dev

38 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] FrameXX@discuss.tchncs.de 6 points 9 months ago* (last edited 9 months ago) (1 children)

Isn't this a problem with every package/library system? Is there really a solution to this that doesn't limit packages with how they handle their dependencies?

This may also be about trust. npm probably could limit a number of dependencies that a single package can have with an arbitrary limit, but they don't do that, because they trust the developers they won't misuse their options. Well...

[–] dependencyinjection@discuss.tchncs.de 1 points 9 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.