<p dir="auto">i think package.json shouldn't be deprecated, but changed: the current proposal suggest full urls in the imports; i suggest the full urls will reside on the package.json, along with the version, and have a semantic short-name for the imported package, so it would be easier to refer to it from the multitudes of projects files... Also, i'd suggest an option to provide a repository short-name in the package.json, so make the more readable.</p>
<p dir="auto">example:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="{
  repositories: {
    kuku: 'https://www.github.com/kuku/'
  },
  dependencies: {
    matrices: '@kuku/matrix-utils@~2.0.0'
   }
}"><pre class="notranslate"><code class="notranslate">{
  repositories: {
    kuku: 'https://www.github.com/kuku/'
  },
  dependencies: {
    matrices: '@kuku/matrix-utils@~2.0.0'
   }
}
</code></pre></div>
<p dir="auto">the usage is simple:</p>
<p dir="auto">my-code.ts:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="import {multiply} from 'matrices' // or perhaps  import {multiply} from '@matrices' 
...
...
"><pre class="notranslate"><code class="notranslate">import {multiply} from 'matrices' // or perhaps  import {multiply} from '@matrices' 
...
...

</code></pre></div>
<p dir="auto">Very interesting project! I love the web-compatibility goal.</p>
<p dir="auto">One thing that would help there is support for bare module specifiers via package name maps: <a href="https://github.com/domenic/package-name-maps">https://github.com/domenic/package-name-maps</a></p>
<p dir="auto">This would allow for imports like:</p>
<div class="highlight highlight-source-js notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="import * as _ from 'lodash';"><pre class="notranslate"><span class="pl-k">import</span> <span class="pl-c1">*</span> <span class="pl-k">as</span> <span class="pl-s1">_</span> <span class="pl-k">from</span> <span class="pl-s">'lodash'</span><span class="pl-kos">;</span></pre></div>
<p dir="auto">Without any requirements on a specific package manager. It's our hope that npm, yarn and others will produce package-name maps during installation, giving you a bridge there. We have a reference implementation in progress here: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="323321191" data-permission-text="Title is private" data-url="https://github.com/WICG/import-maps/issues/37" data-hovercard-type="pull_request" data-hovercard-url="/WICG/import-maps/pull/37/hovercard" href="https://github.com/WICG/import-maps/pull/37">WICG/import-maps#37</a></p>