←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.306s | 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 #
avtolik ◴[19 Nov 24 09:57 UTC] No.42181720[source]▶
Why do you think so? I have 10+ years old Java/Maven projects that build and run fine.
replies(1): >>42185591 #
1. fbn79 ◴[19 Nov 24 16:59 UTC] 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.