Trex: A package manager for Deno (opens in new tab)

Not really for people who have their shells configured to auto-(de)capitalize the name of a command or binary, but for those that don't, it's a departure from what's normal. It's easily solved through an alias or similar, but still: why introduce the impedance?

In my opinion, Trex is actually working against what npm introduced to Node. Though I don't exactly know what "main problem" you're referring to, I can say that:

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.

not really since it is around imports map something native to deno, the purpose is to make it something familiar like npm

Indeed, this is a massive issue with any url based imports. Because Trex supports nest.land, this is not an issue. nest.land is actually a first-of-its-kind blockchain module registry and CDN. Because we use the blockchain for storing modules, they can never be deleted or altered in any way. This also means that they are permanently and indefinitely resolvable from the web. Because of this, module vendoring is no longer an issue!

I do it a ton. I don't write production code much anymore; it tends to be quick scripts or little one-off apps. So I probably type `npm i ...` a few times a day.

Plus things like `npm install` on pull requests, etc.