←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.726s | source
Show context
RadiozRadioz ◴[19 Nov 24 14:39 UTC] No.42183900[source]▶
I call this phenomenon "node rot". Judging by the comments here, it seems like a universal experience.

My favorite is the way that Python projects rot. Not only does Python's setuptools give you all the fun that node-gyp does, the common practice of versioning packages with packagename>=1.25.5 means you're almost guaranteed breakages as pip installs newer versions of packages than what the project was built with.

replies(4): >>42184392 #>>42185344 #>>42191174 #>>42201978 #
1. lexlambda ◴[19 Nov 24 16:37 UTC] No.42185344[source]▶
And project specifying "requires python 3.X+" instead of Version X to Y is also a major culprit I often encounter.

Most of the times it will not work with the newest shiny python, which I only notice after already installing it and then having searched search the Github issues.

replies(1): >>42209854 #
2. __MatrixMan__ ◴[21 Nov 24 23:47 UTC] No.42209854[source]▶
That happens to me all the time. It helped cement my habit of binding the python version to the project with direnv and a flake.nix so I end up switching to the right version when I cd to the project dir.