this post was submitted on 06 Aug 2023
145 points (97.4% liked)

Programming

17374 readers
293 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

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
145
Why is the Node ecosystem so demanding? (sh.itjust.works)
submitted 1 year ago by planish@sh.itjust.works to c/programming@programming.dev
55 comments fedilink hide all child comments
 

Steps to reproduce:

  1. Start a Node project that uses at least five direct dependencies.
  2. Leave it alone for three months.
  3. Come back and try to install it.

Something in the dependency tree will yell at you that it is deprecated or discontinued. That thing will not be one of your direct dependencies.

NPM will tell you that you have at least one security vulnerability. At least one of the vulnerabilities will be impossible to trigger in your particular application. At least one of the vulnerabilities will not be able to be fixed by updating the versions of your dependencies.

(I am sure I exaggerate, but not by much!)

Why is it like this? How many hours per week does this running-to-stay-in-place cost the average Node project? How many hours per week of developer time is the minimum viable Node project actually supposed to have available?

you are viewing a single comment's thread
view the rest of the comments
[–] AA5B@lemmy.world 21 points 1 year ago (1 children)

They’re all that way: it’s just that Node is automatic enough to notice more easily, plus had an insane number of small dependencies

We started doing vulnerability scans on every build, which sounds like a good idea. However, now I know: Java is exactly the same. We need to constantly update but all too often there is no update available yet

[–] Cqrd@lemmy.dbzer0.com 3 points 1 year ago* (last edited 1 year ago) (1 children)

C# is also exactly the same, you just don’t get yelled at when things are out of date and you only see that if you go to manually install packages

[–] kogasa@programming.dev 3 points 1 year ago (1 children)

In C# you can automatically generate (or manually write) binding redirects that let you say "anything using versions between x.y.0 and x.y.9 should use x.y.9", which helps a lot with transitive dependencies. However, doing this manually is hard, and you can't really rely on semver to be done "correctly." This leads to subtle bugs. Occasionally not so subtle, but hard to diagnose.

[–] Urik@lemmy.ca 1 points 1 year ago* (last edited 1 year ago)

I think NPM has the same feature, it's called overrides https://docs.npmjs.com/cli/v9/configuring-npm/package-json?v=true#overrides