4 ms·
I manage a 4year old 'vanilla' typescript app at work. It doesnt't really do anything 'wild', looking at it you would think 'that could be built with anything/n
by fifticon 3y ago
I manage a 4year old 'vanilla' typescript app at work. It doesnt't really do anything 'wild', looking at it you would think 'that could be built with anything/nothing'.
But if you check node-modules, it contains ~1500 npm packages!
Your second thought might be 'oh, its because they let themselves use a huge amount of random gizmos!'.
Nope.. the actual root dependencies are relatively small in number, maybe 30-40 core dependencies.
The problem is, that the prevailing attitude in the ecosystem is to 'just use dependencies', for anything, like lpad.
As 'I know, we'll just use the creditcard my daddy gave me'.
As long as your daddy is rich, you won't see a problem.
If your daddy isnt rich, you will notice that every 10 days as you run npm-build, it will proclaim 'hooray, there are now again 10-15 high-medium security in your 1500 dependencies'.
Combine this need to npm update continuously, with frontends happy disregard for typechecking and backwards compatibility, and you have a recipe for the plague,which we are currently living :-(
- ivanjermakov 3y ago> small in number, maybe 30-40 core dependencies I consider 40 to be a lot, even for a huge enterprise project. I think without major refactoring half of them can be replaced with simple utility functions.
- deleted 3y ago[deleted]