Comment by m4rtink 2 days ago Established Linux distributions. 3 comments m4rtink Reply moritzwarhier 2 days ago Sure. But I'm not sure if I wanted to burden their package registry maintainers with maintaining all kinds of JS/TS packages?And if you go for custom registries, what's the big difference to npm registry?I don't understand it :)One good thing about npm ecosystem IMO is that it's frowned upon to depend on system globals. pianopatrick 6 hours ago There are already quite a few JS / TS packages in the Debian repos. Some examples:https://packages.debian.org/trixie/node-pg https://packages.debian.org/trixie/webpack https://packages.debian.org/trixie/eslintSo someone is already taking on that burden. m4rtink 18 hours ago Maybe that's another indication of something wrong - the NPM ecosystem granularity being so high there is not enough humans alive to safely maintain all the packages ? And some rethinking might be needed even there.
moritzwarhier 2 days ago Sure. But I'm not sure if I wanted to burden their package registry maintainers with maintaining all kinds of JS/TS packages?And if you go for custom registries, what's the big difference to npm registry?I don't understand it :)One good thing about npm ecosystem IMO is that it's frowned upon to depend on system globals. pianopatrick 6 hours ago There are already quite a few JS / TS packages in the Debian repos. Some examples:https://packages.debian.org/trixie/node-pg https://packages.debian.org/trixie/webpack https://packages.debian.org/trixie/eslintSo someone is already taking on that burden. m4rtink 18 hours ago Maybe that's another indication of something wrong - the NPM ecosystem granularity being so high there is not enough humans alive to safely maintain all the packages ? And some rethinking might be needed even there.
pianopatrick 6 hours ago There are already quite a few JS / TS packages in the Debian repos. Some examples:https://packages.debian.org/trixie/node-pg https://packages.debian.org/trixie/webpack https://packages.debian.org/trixie/eslintSo someone is already taking on that burden.
m4rtink 18 hours ago Maybe that's another indication of something wrong - the NPM ecosystem granularity being so high there is not enough humans alive to safely maintain all the packages ? And some rethinking might be needed even there.
Sure. But I'm not sure if I wanted to burden their package registry maintainers with maintaining all kinds of JS/TS packages?
And if you go for custom registries, what's the big difference to npm registry?
I don't understand it :)
One good thing about npm ecosystem IMO is that it's frowned upon to depend on system globals.
There are already quite a few JS / TS packages in the Debian repos. Some examples:
https://packages.debian.org/trixie/node-pg https://packages.debian.org/trixie/webpack https://packages.debian.org/trixie/eslint
So someone is already taking on that burden.
Maybe that's another indication of something wrong - the NPM ecosystem granularity being so high there is not enough humans alive to safely maintain all the packages ? And some rethinking might be needed even there.