←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
uludag ◴[18 Nov 24 18:55 UTC] No.42175643[source]▶
The worst part isn't just that it's nearly impossible to run/update an outdated JS project, but that this process will repeat itself ad infinitum.

On the flip side, anything that uses vanilla JS without a build will most likely run just fine, probably till the end of human civilization.

replies(6): >>42175899 #>>42176382 #>>42177202 #>>42182217 #>>42182764 #>>42189088 #
jazzyjackson ◴[18 Nov 24 20:11 UTC] No.42176382[source]▶
YMMV but I had a 4 year old project whose only dependencies were socketio and express and it booted right up. So stick to stable, mature projects and you're likely to be fine.
replies(1): >>42183191 #
1. authorfly ◴[19 Nov 24 13:29 UTC] No.42183191[source]▶
Just watch out because socketio must be version matched for client-server or you will get the most annoying errors and state inconsistencies in the world. That's a scary production update let me tell you. Version 2.3.0 still scares me to this day after trying to upgrade that without production downtime.