News for hackers. Stuff that matters.

A comment on The tragedy of running an old Node project. Parent comment

Re:The tragedy of running an old Node project by em-bee on Monday November 18, 2024 @03:59PM (#42176958)
it took two hours just to get the project running as it was 4 years ago. wait how much time it will take to upgrade everything to new versions.

and dare i say this is the lucky case. i had problems reactivating some older project because some dependencies were not version locked and newer versions of those were incompatible with other versioned ones.

[ Parent | on HN ]
Re:The tragedy of running an old Node project by DecoySalamander on Tuesday November 19, 2024 @06:45AM (#42182397)
It took 2 hours to realize that project build for a specific version of node should be run with that version of node. And even that was self inflicted since author didn't vet dependencies and used something build as a C++ node addon instead of actual JS (my bet it was to have a slightly easier time writing CSS).
[ Parent | on HN ]
Re:The tragedy of running an old Node project by kwertyoowiyop on Tuesday November 19, 2024 @11:07AM (#42184998)
And even though it builds, there’s no guarantee it’ll work properly.
[ Parent | on HN ]