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 fbn79 on Tuesday November 19, 2024 @04:28AM (#42181497)
I would love the author to test and old java/maven project. Node is a paradise compared to that stack.
[ Parent | on HN ]
Re:The tragedy of running an old Node project by avtolik on Tuesday November 19, 2024 @04:57AM (#42181720)
Why do you think so? I have 10+ years old Java/Maven projects that build and run fine.
[ Parent | on HN ]
Re:The tragedy of running an old Node project by fbn79 on Tuesday November 19, 2024 @11:59AM (#42185591)
Maybe you are fortunate or I'm not because in projects I have experienced missing o changed maven repository urls and changed deps packages names or url. And was an hell to fix.
[ Parent | on HN ]
Re:The tragedy of running an old Node project by cies on Tuesday November 19, 2024 @05:34AM (#42181950)
The only problems I've run into are related to certain package repos that went offline. So you have to track down suitable versions of certain packages on other repos.

OTOH with Node I always find myself in dependency hell with dealing with old projects.

[ Parent | on HN ]
Re:The tragedy of running an old Node project by fbn79 on Tuesday November 19, 2024 @11:57AM (#42185570)
In my experience this only happen if the project does not have a lock file and does not specify a node version (two good practice that must be followed).
[ Parent | on HN ]
Re:The tragedy of running an old Node project by cies on Thursday November 21, 2024 @08:44AM (#42204225)
I'm talking about upgrading dependencies. Something that's rarely easy in a JS/TS project with lots of dependencies.
[ Parent | on HN ]