←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: 0s | 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 #
arp242 ◴[18 Nov 24 19:53 UTC] No.42176217[source]▶
Well, the "solution" ended up as "I gave up and just installed an old Node version and called it a day". So those 2 hours weren't even enough.

I've been using Jekyll/Ruby since 2014 for my website, with a few custom plugins I wrote myself. And I've never really needed to do anything like this. It "just works".

My Go and C programs are the same: "just works". I have some that are close to a decade old.

replies(4): >>42176445 #>>42181328 #>>42181355 #>>42182182 #
Aeolun ◴[19 Nov 24 09:05 UTC] No.42181355[source]▶
Every single time I clone anything Go, I first spend a few hours sorting out dependency issues.
replies(1): >>42182509 #
segfaltnh ◴[19 Nov 24 12:01 UTC] No.42182509[source]▶
This shocks me, what sort of issues do you hit?
replies(2): >>42182797 #>>42185025 #
1. Aeolun ◴[19 Nov 24 16:10 UTC] No.42185025{4}[source]▶
Mainly weird issues of incompatible dependencies, maybe sometimes something that won’t compile because it’s missing a system dependency? I also feel like it sometimes pulls a newer or older dependency that is the missing some used module.