<p dir="auto">Deno bundle is awesome, I can drop countless NPM tooling for a non-deno specific project.</p>
<p dir="auto">One question is how to generate typescript definition files from the bundler, as that would provide the interfaces to code against the es module file generated by the bundle command.</p>
<p dir="auto">It seems that specifying a config as below has no effect.</p>
<div class="highlight highlight-source-json notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="{
  &quot;compilerOptions&quot;: {
    &quot;declaration&quot;: true,
    &quot;sourceMap&quot;: true
  }
}"><pre class="notranslate">{
  <span class="pl-ent">"compilerOptions"</span>: {
    <span class="pl-ent">"declaration"</span>: <span class="pl-c1">true</span>,
    <span class="pl-ent">"sourceMap"</span>: <span class="pl-c1">true</span>
  }
}</pre></div>
<p dir="auto">With <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="523264961" data-permission-text="Title is private" data-url="https://github.com/denoland/deno/issues/3352" data-hovercard-type="pull_request" data-hovercard-url="/denoland/deno/pull/3352/hovercard" href="https://github.com/denoland/deno/pull/3352">#3352</a>, bundles are going to be a mechanism to distribute "libraries" in Deno.  It is logical that someone might want to use a distribution bundle in another Deno workload (or consume it in other runtimes) and would want to have type safe consumption of those files, therefore we should generate the declarations along with a bundle.</p>
<p dir="auto">Related to <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="453754839" data-permission-text="Title is private" data-url="https://github.com/denoland/deno/issues/2475" data-hovercard-type="issue" data-hovercard-url="/denoland/deno/issues/2475/hovercard" href="https://github.com/denoland/deno/issues/2475">#2475</a>.</p>