3 ms·
I sympathize with this. I wanted to use, and slightly modify, a small web app I found on GitHub. Despite it being client-side only, it used node. An older ver
by tyingq 6y ago
I sympathize with this. I wanted to use, and slightly modify, a small web app I found on GitHub.
Despite it being client-side only, it used node. An older version, with older versions of webpack, Babel, and so on. And tons of now deprecated npm packages. It was only a couple of years old.
The only way I could make it work, after days of trying, was a docker container of an older Linux distro. I did try just upgrading packages, but the avalanche of dependency hell made that literally impossible.
I have not had this experience with any other language.
Edit: Noting I have had to update/upgrade older Perl, Python, etc, projects. And they weren't all easy. But they were at least possible. Dozens of things to chase down. Not hundreds.
- r_police 6y agoYeah, because package-lock.json files were never a thing.
- greggman3 6y agoI've had the opposite experience trying to get python and/or ruby not to trash my global environment and various things wanting the system to be setup for their versions and libraries. I like that NPM by default makes all dependencies local and npm lets you include your dev dependencies local to that project. Note: I know their are magic incantations for python and ruby to get them to make everything project local but they aren't what python and ruby do by default.