For the same number of times as in days I'm torn on wether this is good.
On one hand, it's a bridge for node people and adds some nice comfort tooling.
On the other, it means you don't get to really understand how packages and bundling are supposed to work.
I may just end up writing a post on this tonight.
1) Trex is supporting multiple module registries, not just one. (Thus not necessarily centralized) 2) Trex is not associated with one entity in particular. This means that they have no company dedicated to hosting modules in house (another reason that they aren't centralized) 3) Node's package.json included many other things than just imports. Using Trex is completely optional, and if you do use it, an import map does not hinder one's development workflow. In my opinion, it makes dependencies easier to manage.