<p dir="auto"><strong>Describe the bug</strong><br>
When the deno extension is enabled, typed imports via <code class="notranslate">/** @type {import("...</code> stop working.</p>
<p dir="auto"><strong>To Reproduce</strong></p>
<ol dir="auto">
<li>Create <code class="notranslate">Bar.js</code>:</li>
</ol>
<div class="highlight highlight-source-js notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="export class Bar {}"><pre class="notranslate"><span class="pl-k">export</span> <span class="pl-k">class</span> <span class="pl-v">Bar</span> <span class="pl-kos">{</span><span class="pl-kos">}</span></pre></div>
<ol start="2" dir="auto">
<li>Create <code class="notranslate">Foo.js</code>:</li>
</ol>
<div class="highlight highlight-source-js notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="/** @type {import(&quot;./Bar.js&quot;).Bar} */
const foo = null;"><pre class="notranslate"><span class="pl-c">/** <span class="pl-k">@type</span> {import("./Bar.js").Bar} */</span>
<span class="pl-k">const</span> <span class="pl-s1">foo</span> <span class="pl-c1">=</span> <span class="pl-c1">null</span><span class="pl-kos">;</span></pre></div>
<ol start="3" dir="auto">
<li>Hover over <code class="notranslate">foo</code> and note it's type is set to <code class="notranslate">Bar</code>.</li>
<li>Enable deno with <code class="notranslate">Deno: Initialize Workspace Configuration</code></li>
<li>Hover over <code class="notranslate">foo</code> again.</li>
</ol>
<p dir="auto"><strong>Expected behavior</strong><br>
The type remains set to <code class="notranslate">Bar</code>, rather than <code class="notranslate">any</code>.</p>
<p dir="auto"><strong>Screenshots</strong></p>
<p dir="auto">If applicable, add screenshots to help explain your problem.</p>
<p dir="auto"><strong>Versions</strong></p>
<p dir="auto">vscode: 1.62.3 deno: 1.16.3 extension: 3.9.2</p>
<p dir="auto">JS bundlers have a lot of complexity and we do not want to take on all that complexity in Deno. We believe this can be done effectively in "user space" - that is, it doesn't need to be built into the Deno executable. <a href="https://packup.deno.dev/" rel="nofollow">Packup</a> is an example of a Deno program which utilizes esbuild-wasm to provide complex bundling abilities.</p>
<p dir="auto">Ultimately we'd like to remove <a href="https://github.com/denoland/deno/blob/90e3abe8f9aa536809e89b1e232845f3a6d7604d/cli/Cargo.toml#L80">swc_bundler dependency completely</a> completely from Deno.</p>