←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
__MatrixMan__ ◴[19 Nov 24 14:31 UTC] No.42183819[source]▶
> Two hours of my life gone, just to pick up where I left off.

If I had only wasted two hours every time I had to use npm for some reason I'd be significantly ahead of where I am now.

replies(1): >>42198455 #
kiru_io ◴[20 Nov 24 21:46 UTC] No.42198455[source]▶
Doesn't that apply to any it-issues you don't know how to solve?
replies(1): >>42209754 #
1. __MatrixMan__ ◴[21 Nov 24 23:29 UTC] No.42209754[source]▶
no, most of the time when a README says:

> run command xyz

I run xyz and I'm on to the next step in an average of ten or fifteen minutes (because yeah, stuff still goes wrong some times).

But if the instruction is to invoke npm, there's always some crazy side quest involved. It doesn't get any better with time because next time around it's a totally different side quest. I can't even offer any criticism towards fixing it, it just sucks for unique new reason every time.