Why is the Node ecosystem so demanding?

Submitted ⁨⁨1⁩ ⁨year⁩ ago⁩ by ⁨planish@sh.itjust.works⁩ to ⁨programming@programming.dev⁩

Steps to reproduce:

Start a Node project that uses at least five direct dependencies.
Leave it alone for three months.
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?

source

Comments

Sort:hotnew top

Sigmatics@lemmy.ca ⁨1⁩ ⁨year⁩ ago
Because 99% of Node projects are web related, and if something’s vulnerable on the web it won’t take long to be abused

source
- OddFed@feddit.de ⁨1⁩ ⁨year⁩ ago
  Hey, a good answer! 🙌
  
  source
  - elbarto777@lemmy.world ⁨1⁩ ⁨year⁩ ago
    Danke!
    
    source
    -> View More Comments
- BrianTheeBiscuiteer@lemmy.world ⁨1⁩ ⁨year⁩ ago
  Also a great disadvantage with JavaScript being the official scripting language of the web so it needs to work in every browser, but not every browser will implement it the same way. Syntax between the browser and servers also gets conflated.
  
  Conversely, I’ve done frontend development in Java and it sucks major ass. The “advantage” of using one language for the whole project really ended up as a net negative.
  
  source
  - Vipsu@lemmy.world ⁨1⁩ ⁨year⁩ ago
    Fron-end development with Java? You mean Java applets or something?
    
    source
    -> View More Comments
kibiz0r@midwest.social ⁨1⁩ ⁨year⁩ ago
So many reasons. JS has a small standard library, a history of competing standards for things like asynchrony and modules, there are tons of different implementations against tons of different specs, running in tons of different environments (whose constraints and opportunities are also changing all the time), it tends to be the first language to receive an SDK for many services, packages tend to be almost-excessively granular because optimizing for size can be so important on certain platforms (tree-shaking and minification works, but takes time), there are many add-on languages like JSX and TS, there are tons of bundlers and transpilers which each have their own quirks… and also due to its unique position as the lingua franca of client-side web, it tends to be the primary battleground for researchers, tech firms, VR, FOSS, malicious users, and everything else.

To stay alive in an ecosystem like that, any project must become a “ship of theseus” kind of deal.

source
LaSaucisseMasquee@jlai.lu ⁨1⁩ ⁨year⁩ ago
If you set the versions of your dependencies in the package.json file, you’ll reinstall exactly the same ones.

You may get new vulnerability warnings popping up, but what is the issue here ? You’d rather not be aware that a vulnerability has been found since your last development ?

source
- heeplr@feddit.de ⁨1⁩ ⁨year⁩ ago
  
  You’d rather not be aware that a vulnerability has been found since your last development ?
  
  I’d rather develop with dependencies that don’t have so many vulnerabilities.
  
  source
  - LaSaucisseMasquee@jlai.lu ⁨1⁩ ⁨year⁩ ago
    Yeah we all wanna do that, but nobody writes perfect code.
    
    source
    -> View More Comments
  - odbol@lemmy.world ⁨1⁩ ⁨year⁩ ago
    Then you’re in the wrong industry…
    
    source
    -> View More Comments
- planish@sh.itjust.works ⁨1⁩ ⁨year⁩ ago
  I’m struggling to understand how there can be so many security flaws, even in things that don’t seem to matter for security. I think the bar for a security problem might be too low; a lot of these look like footguns that could give my package a security hole, rather than genuine security flaws in the packages they are reported on.
  
  Here’s a progress bar package with a “high” security vulnerability because it contains an internal utility that merges objects and doesn’t stop you writing to the prototype. Did the progress bar package ever promise to provide an object merge function that was safe to use on untrusted user input?
  
  Here’s a notification UI element that bills using HTML in your notification messages as a feature. It has a “medium” level “XSS” security vulnerability where the message parameter is not sanitized to remove HTML. A CVE was issued for this.
  
  Here’s an arbitrary code execution vulnerability in sqlite3! High severity! The bug is that, if you tell sqlite3 to substitute an object into an SQL statement, it will run the ToString() method on the object. If an evil hacker has broken into your lead developer’s house and written a malicious ToString() method into one of the classes of object you use as a database query parameter, then that code would run! The fix here was, instead of letting the normal Javascript stringification rules apply, to hardcode all objects to be inserted into the database as “[object Object]”, because surely that is what the programmer meant to store.
  
  source
  - nick@campfyre.nickwebster.dev ⁨1⁩ ⁨year⁩ ago
    You don’t need to do anything when you get a security advisory if you’re not impacted or the risk is acceptable. They’re just there to advise you.
    
    source
    -> View More Comments
  - faintbeep@lemm.ee ⁨1⁩ ⁨year⁩ ago
    There’s a whole industry of bug bounty hunters making money off this trivial stuff. At work I had to fix a “bug” which could only be exploited if an attacker took control of facebook first, and even then it just meant a user could be redirected to a different website. And the company paid the clown that found the “vulnerability”.
    
    source
- AA5B@lemmy.world ⁨1⁩ ⁨year⁩ ago
  
  If you set the versions of your dependencies in the package.json file
  
  Or if you leave that alone, and update your package-lick.json so can install exact dependencies with npm ci
  
  source
ono@lemmy.ca ⁨1⁩ ⁨year⁩ ago
My take: It’s because the “trust everything from everybody” model is fundamentally broken.

Note that the “trust” here is not only about avoiding malicious or vulnerable code, but also about dependability. Even if you ignore the “supply chain” security problems inherent in this model, it practically guarantees that breakage like this will happen.

This is part of why I prefer languages with robust standard libraries, and why I am very picky about third party dependencies.

source
- odbol@lemmy.world ⁨1⁩ ⁨year⁩ ago
  What languages are those? And if you say C/C++ I’m going to laugh
  
  source
  - planish@sh.itjust.works ⁨1⁩ ⁨year⁩ ago
    The C++20 or so STL actually has things in it now.
    
    source
    -> View More Comments
- howlongisleft@lemmy.world ⁨1⁩ ⁨year⁩ ago
  Thank god for proxy registries. I love Node, but it’s like using a house of cards as the foundation of a skyscraper.
  
  source
  - BrianTheeBiscuiteer@lemmy.world ⁨1⁩ ⁨year⁩ ago
    The fact that NPM can’t use multiple registries (yes, I know about scoped registries) is astounding. For every other language my org will separate artifacts into half a dozen or so virtual repos. The artifact team is quite annoyed that Node/JavaScript has to all go into one uber-repo.
    
    source
- lemann@lemmy.one ⁨1⁩ ⁨year⁩ ago
  I personally don’t trust NodeJS libraries that much - I always run projects inside Docker as a regular user with access to the working directory, just in case the supply chain is poisoned.
  
  In the case of Python, particularly when I was testing out the LLaMA model, I just stood up a new VM for that. Back then safetensors wasn’t a thing, and the model tensor file format (python pickle-based) could potentially store arbitary code.
  
  Robust standard libraries are amazing to have.
  
  source
bouncing@partizle.com ⁨1⁩ ⁨year⁩ ago
At least part of it is that JavaScript is not really a batteries included language like Python or Java to even PHP.

You can’t really do anything productive without relying on a third party library.

source
- elbarto777@lemmy.world ⁨1⁩ ⁨year⁩ ago
  This is not universally true. You totally can, especially today.
  
  source
- BrianTheeBiscuiteer@lemmy.world ⁨1⁩ ⁨year⁩ ago
  Most of those are server-side languages and I’d disagree with the assessment. For web services Java needs some kind of server like Jetty, Undertow, or Tomcat. For testing you need JUnit or NGTest. And for common, everyday utilities you need something like Apache Commons or Guava. These things don’t “ship” with Java (and there’s actually a fair amount of runtimes now, it’s not only Oracle).
  
  The thing that seems to benefit Java over Node is major corporate support (Oracle, RedHat, IBM) so for better or worse you can usually rely on a handful of essential tools being updated regularly.
  
  source
  - bouncing@partizle.com ⁨1⁩ ⁨year⁩ ago
    I wouldn’t say you need no dependencies in a Java project, but by all means check the average number of dependencies you get with Java or Python and compare it to almost any Node project.
    
    You could probably sample projects on GitHub, look at the dependency graph, and compare.
    
    source
- lemmyvore@feddit.nl ⁨1⁩ ⁨year⁩ ago
  All the languages you mentioned have some core APIs included and need to rely on third party libraries for more.
  
  source
  - bouncing@partizle.com ⁨1⁩ ⁨year⁩ ago
    Yes, that’s true, but JavaScript has very few core APIs aside from basic DOM manipulation. Even things like comparing timezones requires a third party dependency, for example.
    
    source
AA5B@lemmy.world ⁨1⁩ ⁨year⁩ ago
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

source
- Cqrd@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago
  C# is also exactly the same, you just don’t get yelled out when things are out of date and you only see that if you go to manually install packages
  
  source
  - kogasa@programming.dev ⁨1⁩ ⁨year⁩ ago
    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.
    
    source
    -> View More Comments
Paradox@lemdro.id ⁨1⁩ ⁨year⁩ ago
For most projects or tools that I find on GitHub these days, I run them all in docker. Node, at least, is somewhat of a good guest. All it’s crap lives in node_modules, and so when I’m done, rm the directory and it’s all clean. Python seems to love leaving relics across my system

source
Treczoks@lemm.ee ⁨1⁩ ⁨year⁩ ago
Welcome to my world. Not that I’m using node, but I’m using mediawiki. They manage to f-up something with about every update, and the documentation, if it exists at all, is often enough completely wrong or broken.

source
- ck_@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago
  Been there, Mediawiki is truely painful, especially if you are trying to maintain an extension or two “on the side”.
  
  source
  - Treczoks@lemm.ee ⁨1⁩ ⁨year⁩ ago
    That is exactly the case here. I’ve got a private wiki with a rather large extension by now, and it is the only PHP project I have. So whenever mediawiki f-cks something up, which is nearly every update, I restart my PHP skills to find and fix the sh-t they did to my code this time.
    
    source
lysdexic@programming.dev ⁨1⁩ ⁨year⁩ ago

Something in the dependency tree will yell at you that it is deprecated or discontinued.

Only if you didn’t pinned the dependencies you actually consume, and expect that all your dependencies magically comply with semver.

Blindly replacing dependency versions never worked, at least reliably. If you do not put in the work to ensure things work, more often than not you’ll be surprised by them not working.

source
- agressivelyPassive@feddit.de ⁨1⁩ ⁨year⁩ ago
  Then you’ll end up with tons of vulnerabilities within days. That can’t be the solution either.
  
  source
  - lysdexic@programming.dev ⁨1⁩ ⁨year⁩ ago
    
    Then you’ll end up with tons of vulnerabilities within days.
    
    You only end up with vulnerabilities if you refuse to update your dependencies. Updating a dependency is something you need to do yourself, along with running build validation tests after a successful update. Just because npm can download newer packages that does not mean those packages are good.
    
    source
    -> View More Comments
- planish@sh.itjust.works ⁨1⁩ ⁨year⁩ ago
  Often it seems that people will make patch releases that add a “feature” of complaining at install time that that major release/minor release/entire package is bad now and should be replaced with something else. It still works, but it annoys everyone who transitively depends on it forevermore.
  
  source
peereboominc@lemm.ee ⁨1⁩ ⁨year⁩ ago
I wonder if it has something to do with the framework you pick. There are probably frameworks that aim to be as stable as possible but lack the cutting edge.

source
- agressivelyPassive@feddit.de ⁨1⁩ ⁨year⁩ ago
  And these frameworks will fall out of fashion in three days.
  
  source
heeplr@feddit.de ⁨1⁩ ⁨year⁩ ago
It’s a job machine. Maintenance is easier than improving code quality or adding features.

source