←back to thread

The tragedy of running an old Node project

(abdisalan.com)
272 points abdisalan | 1 comments | 18 Nov 24 18:24 UTC | HN request time: 0.001s | source
Show context
mvkel ◴[18 Nov 24 19:03 UTC] 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 #
fbn79 ◴[19 Nov 24 09:28 UTC] 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 #
cies ◴[19 Nov 24 10:34 UTC] 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 #
fbn79 ◴[19 Nov 24 16:57 UTC] 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 #
1. cies ◴[21 Nov 24 13:44 UTC] No.42204225[source]▶
I'm talking about upgrading dependencies. Something that's rarely easy in a JS/TS project with lots of dependencies.