pkg

I don't remember the details, and cannot find my notes on vercel/pkg. But looking at https://github.com/vercel/pkg right now I see the project has been deprecated in favour of single-executable-applications

> Standalone CLI — we haven’t worked on a standalone CLI for the new engine yet, but will absolutely have it before the v4.0 release. This part is the most exciting to me. Given the rest of the release announcement, I'm assuming this means that it'll be built in Rust rather than embed Node. While I'm not a Rust zealot of anything, I'm very partial to not embedding Node. Particularly when it depends on using Vercel's now-abandoned pkg[1] tool. [1] https://github.com/vercel/pkg

Nodejs support for "single executable applications" is getting there - this issue below is preventing wider adoption at the moment: "The single executable application feature currently only supports running a single embedded script using the CommonJS module system." https://nodejs.org/api/single-executable-applications.html Should be an awesome game changer for node.js when the feature gets rounded out. Also check out vercel's `pkg`: https://github.com/vercel/pkg/issues/1291

There is also https://github.com/vercel/pkg

> I'm assuming having to bundle all of Node.js/V8 in your executable is one of them I guess you could expect Linux distros to come with Node (though it's probably a quite dated release). Looking at standalone binaries, both bun.sh and Node.js are about 30MB. In comparison, Python 3.10 is 9MB and starts slower than bun but faster than Node. Bundling is easy too, you can take a loot at vercel/pkg https://github.com/vercel/pkg

You don't even need that: https://github.com/vercel/pkg. I think there are equivalents in the Python ecosystem.

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.

There is also Pkg from Vercel for those things. Happy user. Package your Node.js project into an executable https://github.com/vercel/pkg

See: Distroless images[0] This is one of the huge benefits of recent systems languages like go and rust -- they compile to single binaries so you can use things like scatch[1] containers. You may have to fiddle with gnu libc/musl libc (usually when getaddrinfo is involved/dns etc), but once you're done with it, packaging is so easy. Even languages like Node (IMO the most progressive of the scripting languages) have packages like vercel/pkg[2] which produce native binaries. BTW if you're considering running redis these days... Check out KeyDB[3], it's impressive. There are a lot of redis alternatives with interesting features these days that I wonder if running vanilla redis is even a good idea anymore (outside of ensuring complete feature-set compatibility). [0]: https://github.com/GoogleContainerTools/distroless [1]: https://hub.docker.c

An alternative to Electron I like is Vercel Pkg https://github.com/vercel/pkg . You write a server in Node.js, compile it to an exe with Vercel Pkg and users run the exe on their local machine and use it with their browser. Instead of running an app "in the cloud" they run it on the server on their machine. But the server could easily also be moved to the cloud as well. Using a browser to connect to an app running on your local machine has the nice feature that you can open any number of browser-views on it, looking at the app and your data and tools from multiple viewpoints. Since it is local they are the only user and don't need to login or "keep a session" and can thus interact with the app in multiple ways in parallel. I don't need to design in a feature that allows users to "open a new window". That is handled by the browser. Open a

I've personally used `nexe` before and ended up swapping it out for Vercel's `pkg`[1]. `pkg` worked better with building ARM binaries and with less gotchas with multiplatform builds, in my experience. [1]: https://github.com/vercel/pkg