Programming

13384 readers

1 users here now

All things programming and coding related. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

remington

alyaza

Hexorg

Do i really need 100 node modules to only get one to work? (feddit.it)

submitted 1 year ago* (last edited 1 year ago) by dontblink@feddit.it to c/programming

13 comments fedilink hide all child comments

This seem quite counter intuitive and to be bloating the project: i'm trying to install tsdoc linter, but npm adds like other 50 packages alongside with it, is this the expected behaviour? Why is it so?

A project that could easily be 5MB ends up being like 60MB

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

[–] MaggiWuerze@feddit.de 37 points 1 year ago* (last edited 1 year ago) (4 children)

That's because the web dev ecosystem at one point decided, that libraries that only offer very minute functionality are acceptable as well as adding 20 of them to your project.

Examples like isEven or leftPad come to mind, which have such high proliferation, that their dev broke half the planets web projects when he broke them intentionally.

[–] brunofin@lemm.ee 8 points 1 year ago (1 children)

I remember reading about this years ago, even affected internal Facebook dev team when it happened.

[–] JackbyDev@programming.dev 7 points 1 year ago

The dev was (rightfully) angry at NPM about another project and asked NPM to delist all of them. For some reason NPM at the time allowed this. I think they just had never thought about the problems it could cause before. Deployments to package managers, especially open source deployments with irrevocable licences, shouldn't be allowed to be removed. Doubly so once they're depended on. NPM's policy changed and is now more in line with that.

It affected pretty much everyone because some very popular frameworks at the time pulled left pad in transitively through other modules. Then because those popular frameworks did and most everyone was using those frameworks it broke pretty much everyone.

[–] upstream 7 points 1 year ago (1 children)

Step one: Create random package that does something trivial that’s done often.

Step two: Start making PR’s to lots of open source projects replacing a number of lines of code with your new package.

Step three: Work hard to get your package into another package that’s used by many.

Step four: Update your CV to reflect that you build software that thousands of companies depend upon.

Step five: Profit from the stupid incentives created by companies hiring people that pad their CV’s by making redundant software and push them into everything they can to make sure everyday is dependency hell.

[–] emeralddawn45@discuss.tchncs.de 1 points 1 year ago

Gotta make a name somehow. (/s)

load more comments (2 replies)