4 ms·

I would love the author to test and old java/maven project. Node is a paradise compared to that stack.

• avtolik 2y ago
  Why do you think so? I have 10+ years old Java/Maven projects that build and run fine.
  • fbn79 2y ago
    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.
• cies 2y ago
  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.
  • fbn79 2y ago
    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).
    • cies 2y ago
      I'm talking about upgrading dependencies. Something that's rarely easy in a JS/TS project with lots of dependencies.