3 ms·

This feels really short & snide & simplistic to me. I'd like to see you argue the other side of this discussion & see if you have the eye to appreciate what is

This feels really short & snide & simplistic to me. I'd like to see you argue the other side of this discussion & see if you have the eye to appreciate what is better & nicer. There's a lot of complexity that's still way way way away in the rear view mirror. It's still super possible & super nice to use deps.ts to tackle a lot of the current situations. Very side mention on deps.ts, I think there is a bit of missing potential to pass your tree of deps into other packages deps, but this is definitely just working around import-maps's intended use case in userland.

illiarian 4y ago
> It's still super possible & super nice to use deps.ts to tackle a lot of the current situations. You mean: - manually import and re-export every dependency you depend on - cannot change resolution mechanism to a different package repository, for example, in a corporate setting. Especially not for dependencies of dependencies. You could probably automate it by providing a package.json of sorts, and reading from there...