pkg VS deno

You don't even need that: https://github.com/vercel/pkg.

I think there are equivalents in the Python ecosystem.

Another exciting feature is the ability to build a single-executable Node.js binary. Before Node.js v18, the only way to build a Node.js binary was to use a third-party package, like pkg.

As a comparison I am using https://github.com/vercel/pkg to package my Node.js app into an exe file. Vercel-pkg allows me to build different images for different platforms like Windows, Linux, Mac. It would be nice if it could produce a single .exe that worked on all platforms. But I guess such an exe would have to be bigger. It is not too cumbersome to produce one exe per platform that my users need.

To run NodeJS as a sidecar we need to pack it into binary. Taurine is bundling your server code and preparing it for packing into a single binary. Using Vercel’s pkg CLI tool we can compile it into a single executable binary. That binary is running with the Tauri application.

What if you packaged the whole thing into one executable using pkg?

In addition to the other responses, there are node packages like pkg and nexe that you can use to package the node executable and your code into a single executable.

Not really, at last check it just bundles the entire .Net runtime with the compiled image. It's basically the equivalent of https://github.com/vercel/pkg or similar tools.

You can even pack your terminal application in a single binary that does not require separate NodeJS installed via pkg.

import { connect } from "https://deno.land/x/redis/mod.ts"; const redis = await connect({ hostname, port }); let cachedResult = await redis.get(query); let result = cachedResult; if (!cachedResult) { result = db.get(query); await redis.set(query, result); } return result;

This feat: denort binary #9041 used to exist. No longer. I'm pretty sure Node.js doesn't have such capability either - Node.js download doesn't even ship with just the executable - npm and npx are in the download zip - and those files need to be modified to even use npx without installing locally or globally.

Finally, you could use a runtime like Deno which natively supports Typescript.

Why not just use https://deno.land/

Fast iterating thanks to Deno, for built in Typescript debugging and bundling

I usually look at https://github.com/denoland/deno for the releases.

Or you can see the latest release on GitHub Releases page. https://github.com/denoland/deno/releases

I'd run an API using Deno (https://deno.land), and consume that API with an SSR/SSG site built using Astro (https://astro.build). SCSS for styling, and probably just Vanilla JS (written in Typescript and compiled via Deno) — I increasingly find that unless my site is massively interactive, plain old Vanilla JS is totally sufficient.

First, you would need to obtain the source code for the Deno runtime and its dependencies, which you can find on the Deno GitHub repository (https://github.com/denoland/deno).

Reading Deno source code dependcies to build appear to be Rust and V8. listenTls: https://github.com/denoland/deno/blob/f0c79a676cc36a5e8f6f5af86d93186d41974518/ext/net/01_net.js, https://github.com/denoland/deno/blob/f0c79a676cc36a5e8f6f5af86d93186d41974518/ext/net/02_tls.js.