<story><title>Deno 1.6 supports compiling TypeScript to a single executable</title><url>https://github.com/denoland/deno/issues/986#issuecomment-740756795</url></story><parent_chain></parent_chain><comment><author>j1elo</author><text>I&amp;#x27;ve been using vercel&amp;#x2F;pkg with great success, in order to achieve a similar target and package a whole application into a standalone executable:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;vercel&amp;#x2F;pkg&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;vercel&amp;#x2F;pkg&lt;/a&gt;&lt;p&gt;This can be useful for people wanting to do this with Node. It&amp;#x27;s nice to have a single file that can be started right away without any external dependency. And also, it prevents from having to distribute the full sources. Kudos to the Deno devs who have integrated this option directly into the runtime.</text></comment>
<story><title>Deno 1.6 supports compiling TypeScript to a single executable</title><url>https://github.com/denoland/deno/issues/986#issuecomment-740756795</url></story><parent_chain></parent_chain><comment><author>mrkurt</author><text>This is such a good feature. Go has been great for shipping single purpose binaries (like the CLI for &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;fly.io&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;fly.io&lt;/a&gt;), but I really enjoy writing TypeScript more than Go.</text></comment>