Node is a very rapidly expanding ecosystem.
So it does not have the kind of maturity and stability admins are used to dealing with.
Along with that, Debian package release cycles are too slow to keep up with this kind of change.
Canonical has a more rapid release culture, which is why you are seeing the custom ppa's.
But of course, they are not being integrated up and down the OS version tree.
The better approach is actually to use npm (Node Package Manager), to handle dependencies that are not from stable projects.
That keeps your glue layers up to date much better.
(Though you still need to have a good idea where semantic versioning works, or where you are better off locking down a module to a specific version.
That may be more of a Dev concern though.)
Also, some stable projects are better off being installed from source/directly from the project's site.
Because Debian(and Canonical?) sometimes does... unusual... things when they build packages.
Yes. That makes maintenance harder because you don't have everything under the Debian package management system.
But it is the reality of dealing with some kinds of projects.
Debian/Canonical are opinionated, often in a different way than the creators of a particular software.
Sometimes, the software needs to follow its own logic for it to be completely effective.
This is part of the Admin's job... herding cats (software, Os', organisational constituencies).
Slashdot Mirror
Node is a very rapidly expanding ecosystem. So it does not have the kind of maturity and stability admins are used to dealing with. Along with that, Debian package release cycles are too slow to keep up with this kind of change. Canonical has a more rapid release culture, which is why you are seeing the custom ppa's. But of course, they are not being integrated up and down the OS version tree.
The better approach is actually to use npm (Node Package Manager), to handle dependencies that are not from stable projects. That keeps your glue layers up to date much better. (Though you still need to have a good idea where semantic versioning works, or where you are better off locking down a module to a specific version. That may be more of a Dev concern though.)
Also, some stable projects are better off being installed from source/directly from the project's site. Because Debian(and Canonical?) sometimes does ... unusual ... things when they build packages.
Yes. That makes maintenance harder because you don't have everything under the Debian package management system.
But it is the reality of dealing with some kinds of projects. Debian/Canonical are opinionated, often in a different way than the creators of a particular software. Sometimes, the software needs to follow its own logic for it to be completely effective.
This is part of the Admin's job ... herding cats (software, Os', organisational constituencies).