this post was submitted on 22 Jul 2023
41 points (100.0% liked)

Programming

13376 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 1 year ago
MODERATORS
alyaza@beehaw.org
Hexorg@beehaw.org
remington@beehaw.org
41
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@beehaw.org
17 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
[–] upstream@beehaw.org 5 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)