> You don't have to deal with virtualenvs or packages from different projects conflicting.
That's only because you're basically assured there will be conflicts inside any single project. Every time I install anything via npm I get a boatload of warnings about insecure dependencies, which are effectively impossible to fix without breaking the whole mountain of hacks.
There are good deployment stories out there. JS is not one of them.
Re:You don't really need a virtualenv
by nicoburns on Thursday February 04, 2021 @08:52AM
(#26025290)
> That's only because you're basically assured there will be conflicts inside any single project.
That's not an issue with the package management though, that's an issue with the quality of the packages themselves. The JS ecosystem does have issues there. But the tooling itself is good.
Re:You don't really need a virtualenv
by dboreham on Thursday February 04, 2021 @08:14AM
(#26025032)
That one tool must be yarnnpmgypbabelwebpack?
- There's one tool to use, and it comes pre-installed
- You don't have to deal with virtualenvs or packages from different projects conflicting.
- Native code dependencies "just work".