Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: