←back to thread

The tragedy of running an old Node project

(abdisalan.com)
272 points abdisalan | 2 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 #
fourseventy ◴[18 Nov 24 20:03 UTC] No.42176305[source]▶
Sounds like you are way too used to the javascript ecosystem if you think getting an old project to build should take hours...
replies(4): >>42176343 #>>42176528 #>>42185263 #>>42185292 #
viraptor ◴[18 Nov 24 20:08 UTC] No.42176343[source]▶
This is not even JS specific. All of Python / Ruby / other changing runtimes will require some upkeep. Even C recently needs some attention because clang updated default errors.
replies(2): >>42176394 #>>42177183 #
1. Macha ◴[18 Nov 24 20:13 UTC] No.42176394{3}[source]▶
Even some of my Rust projects end up in this state, where updating one library ends up with needing to update interacting libraries.
replies(1): >>42187920 #
2. jakimfett ◴[19 Nov 24 20:47 UTC] No.42187920[source]▶
That sounds pretty frustrating.

When I find my shell scripts from 20+ years ago, they still just run as intended.