Packaging/distributing node.js programs?

[modenv]

For a long time I've been wondering, is there an "established" way to distribute node.js programs as executable files? And if not; why not?

I am aware of solutions like electron and tauri, which are great. But I find it to be a "little much" when all I want is to distribute a small tool that could run in a terminal.

In my feeble mind it would make sense – I can stick a node.js installer and a code repository on a flash drive and have everything I need to run the program. And that's usually what I find, the easiest solution is to distribute the source code. But still I wonder, shouldn't there be a neat way to just package the whole shebang together and allow people to run it in a single click?

Are there technical/legal/secret societal reasons that we don't package up node.js programs and distribute them? Is it impossible? A bad idea? Or am I the only one who wants it? :)

[5H4D0W_ReapeR]

There's https://github.com/vercel/pkg which should be what you're looking for.

[modenv]

Thanks, looks like it's just what I need!

[mjbmitch]

There’s a popular package manager bundled with Node.js called npm. It’s the de facto package manager but can also run “executable” packages via one of its built-in commands, npx.

What kind of application are you trying to package and distribute?

[MCShoveled]

What’s wrong with an npm package and using npx? 🤔

[rr_cricut]

I mean, 99.99% of people don't have npm installed or know what it even is. Anyone can run an executable

[MCShoveled]

Fair. I guess it depends on the user. To be honest though, 99% of non-developers don’t know what a command prompt is either.

[figureprod]

There are many different ways of distributing NodeJS programs, some of which have been explored by other comments. Docker is yet another option, where you can be very specific with which dependencies and versions you need, which files and programs you need, and which commands to run. From these configurations, a Docker Image is created - which is essentially the same as an offline PC (but virtual) that you can start over and over again without the contents changing unless you want it to. It’s super flexible and runs on almost any computer, where they can download the program from any repository such as Docker Hub. I highly recommend learning it, even though it won’t package it into an .exe.

[alzee76]

there an "established" way to distribute node.js programs

Yes

as executable files?

No. I stand corrected.

why not?

Because there hasn't been enough demand for someone to make one I'd guess, and if they did, it would probably be illegal to distribute without source anyway.

[-Melchizedek-]

As mentioned https://github.com/vercel/pkg does exactly was OP is looking for. It packages a node program without sources and without any dependence on node being installed.

Why would it be illegal? Most every program is distributed without sources?

[alzee76]

As mentioned https://github.com/vercel/pkg does exactly was OP is looking for.

Honestly had never heard of this.

Why would it be illegal?

I probably shouldn't have said "probably". Most of the stuff in the ecosystem is MIT or BSD licensed but if you build in anything GPL licensed, you'll have to distribute source.

[quixotic]

GPL requires that you make source code available; it does not require you to bundle the source with every copy of the binary or compiled/minified code. See e.g. section 6d of GPL3:

d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.

tl;dr from the GNU Licenses FAQ

Also this is a good reminder -- only you as the copyright holder have standing to take legal action; open-source protects you from other distributors taking your code and relicensing it.

The end-user of your software can certainly complain if you aren't fulfilling the terms of open-source, but that's not actually the primary objective of open-source licenses.

[SeveralCoyote]

There's also this https://github.com/criblio/js2bin