←back to thread

272 points abdisalan | 6 comments | | HN request time: 0.685s | source | bottom
Show context
mvkel ◴[] No.42175730[source]
> time to run it after not touching it for 4 years

> Two hours of my life gone...

Two hours of work after 4 years sounds ... perfectly acceptable?

And it would have run perfectly right away if the node version was specified, so a good learning, too

This feels like making a mountain out of a mole hill

replies(21): >>42175799 #>>42175818 #>>42175826 #>>42175846 #>>42176217 #>>42176305 #>>42176788 #>>42176958 #>>42181497 #>>42182299 #>>42182564 #>>42182778 #>>42183020 #>>42183093 #>>42183501 #>>42183725 #>>42184814 #>>42192770 #>>42193606 #>>42194518 #>>42211558 #
1. fbn79 ◴[] No.42181497[source]
I would love the author to test and old java/maven project. Node is a paradise compared to that stack.
replies(2): >>42181720 #>>42181950 #
2. avtolik ◴[] No.42181720[source]
Why do you think so? I have 10+ years old Java/Maven projects that build and run fine.
replies(1): >>42185591 #
3. cies ◴[] No.42181950[source]
The only problems I've run into are related to certain package repos that went offline. So you have to track down suitable versions of certain packages on other repos.

OTOH with Node I always find myself in dependency hell with dealing with old projects.

replies(1): >>42185570 #
4. fbn79 ◴[] No.42185570[source]
In my experience this only happen if the project does not have a lock file and does not specify a node version (two good practice that must be followed).
replies(1): >>42204225 #
5. fbn79 ◴[] No.42185591[source]
Maybe you are fortunate or I'm not because in projects I have experienced missing o changed maven repository urls and changed deps packages names or url. And was an hell to fix.
6. cies ◴[] No.42204225{3}[source]
I'm talking about upgrading dependencies. Something that's rarely easy in a JS/TS project with lots of dependencies.