<p dir="auto"><code class="notranslate">deno run [OPTIONS] &lt;SCRIPT_ARG&gt;...</code> doesn't use import maps to resolve <code class="notranslate">&lt;SCRIPT_ARG&gt;</code>. For example, consider:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="$ deno run https://deno.land/std@0.148.0/examples/welcome.ts
Welcome to Deno!"><pre class="notranslate"><code class="notranslate">$ deno run https://deno.land/std@0.148.0/examples/welcome.ts
Welcome to Deno!
</code></pre></div>
<p dir="auto">This could be rewritten to use an import map but that's unsupported:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="$ cat &gt; mods.json &lt;&lt;eof 
{
  &quot;imports&quot;: {
    &quot;std/&quot;: &quot;https://deno.land/std@0.148.0/&quot;
  }
}
eof

$ deno run --import-map=mods.json std/examples/welcome.ts
error: Module not found &quot;file:///home/stephen/tmp/sdfoiunouiwsf/std/examples/welcome.ts&quot;."><pre class="notranslate"><code class="notranslate">$ cat &gt; mods.json &lt;&lt;eof 
{
  "imports": {
    "std/": "https://deno.land/std@0.148.0/"
  }
}
eof

$ deno run --import-map=mods.json std/examples/welcome.ts
error: Module not found "file:///home/stephen/tmp/sdfoiunouiwsf/std/examples/welcome.ts".
</code></pre></div>
<p dir="auto">Allowing <code class="notranslate">&lt;SCRIPT_ARG&gt;</code> to use the import map resolution like the rest of a Deno project is useful for users wishing to keep all their dependency versions in one file. For example, I have a repo with an import map pinned to a specific standard library version:</p>
<div class="highlight highlight-source-js notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="{
  &quot;imports&quot;: {
    // many other imports
    &quot;std/&quot;: &quot;https://deno.land/std@0.148.0/&quot;
  }
}"><pre class="notranslate"><span class="pl-kos">{</span>
  <span class="pl-s">"imports"</span>: <span class="pl-kos">{</span>
    <span class="pl-c">// many other imports</span>
    <span class="pl-s">"std/"</span>: <span class="pl-s">"https://deno.land/std@0.148.0/"</span>
  <span class="pl-kos">}</span>
<span class="pl-kos">}</span></pre></div>
<p dir="auto">And a deno.json with tasks that try to duplicate that version but they often get out of sync and I lose that nice view into seeing all my dependencies in one place:</p>
<div class="highlight highlight-source-json notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="{
  &quot;tasks&quot;: {
    &quot;dev:serve&quot;: &quot;deno -q run --allow-read=. --allow-net https://deno.land/std@0.149.0/http/file_server.ts dist&quot;,
  }
}"><pre class="notranslate">{
  <span class="pl-ent">"tasks"</span>: {
    <span class="pl-ent">"dev:serve"</span>: <span class="pl-s"><span class="pl-pds">"</span>deno -q run --allow-read=. --allow-net https://deno.land/std@0.149.0/http/file_server.ts dist<span class="pl-pds">"</span></span>,
  }
}</pre></div>
<p dir="auto">I'd like it to be:</p>
<div class="highlight highlight-source-json notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="{
  &quot;tasks&quot;: {
    &quot;dev:serve&quot;: &quot;deno -q run --allow-read=. --allow-net std/http/file_server.ts dist&quot;,
  }
}"><pre class="notranslate">{
  <span class="pl-ent">"tasks"</span>: {
    <span class="pl-ent">"dev:serve"</span>: <span class="pl-s"><span class="pl-pds">"</span>deno -q run --allow-read=. --allow-net std/http/file_server.ts dist<span class="pl-pds">"</span></span>,
  }
}</pre></div>
<p dir="auto">First of all, thank you very much. I think deno with built-in typescript support is a great idea.</p>
<p dir="auto">But I don't think that package.json was a bad idea.</p>
<p dir="auto">You could improve it, for:</p>
<ul dir="auto">
<li>repetitive workflows and scripts</li>
<li>application configuration for different environments</li>
<li>linter, prettify rules</li>
<li>maintainer information, licensing, etc</li>
<li>even for docker building</li>
</ul>
<p dir="auto">and so on. It could be the single point of truth without any polling configuration files lying around wild.</p>