3 ms·
It puts those deps in your source tree, sure, but no one advocates committing them to your repository except in few specific scenarios. This kind of thing is a
by IceDane 5y ago
It puts those deps in your source tree, sure, but no one advocates committing them to your repository except in few specific scenarios.
This kind of thing is also pretty much standard for most programming languages today.
- Too 5y agoIsn’t parent explicitly trying to avoid committing the node_modules?
- IceDane 5y agoIt seems to me bitcharmer was railing against the notion that you would have X MB of dependencies in your project folder. I was just pointing out that this is basically standard practice today(and the alternatives are usually awful) and that even if you do have your deps in the project folder, you don't usually check them into version control, so his entire point is moot.
- bitcharmer 5y ago> This kind of thing is also pretty much standard for most programming languages today No, it is not. Have a look at java, golang or rust. None of those languages advocate for embedding deps in your source tree as it's quite clearly a terrible anti-pattern to follow. I wouldn't consider how JavaScript does stuff a good example.