Add the npm package publishing

[firefoxic]

Hello! Great idea and work!

But I'm afraid it will be difficult for me to promote deputui among my colleagues and acquaintances until there is a package on npmjs.com.

Please add the npm package publishing.

[twiddler]

That makes sense. Thanks for the suggestion.

I have never published a binary to npmjs.com before, so I will have to look into that first. If you can point me to a project whose approach I can adopt, that'd be great.

[firefoxic]

Quite a few non-JS projects are published on https://npmjs.com. Among the most recent ones I’ve come across, I can cite https://getfresh.dev as an example, which is also written in Rust.

However, if you look at the code of the published package, you can see that it doesn’t contain the binaries themselves; the JavaScript code simply runs or installs the binary appropriate for the system.

[twiddler]

I notice that I am a bit hesitant to implement this for two reasons:

1. We'd have to either pull the binary on demand (which adds latency), or use a postinstall script (which is generally recommended against for security reasons).
2. Publishing binaries to npm feels a bit awkward to me personally. The binary one pulls will depend on their system's architecture, but still end up in node_modules. That feels a bit polluted to me; I'd rather have node_modules be platform-agnostic. But I realize a lot of projects do publish and pull binaries one way or the other, so I am willing to follow the general practice here.

I notice this is not a high priority task for me right now. If you or someone else would like to implement this, I'd appreciate the contribution! 🙏 I would suggest the following:

1. Do not use postinstall.
2. Add a GitHub action that compiles binaries when a release is added to the GitHub repository.
3. Add a GitHub action that publishes to npmjs.com when a release is added to the GitHub repository. Possibly to @deputui/bin or something.
4. Derive the version tag to publish to npmjs.com from the GitHub release tag, so that we do not have to manually keep things in sync.
5. Have the npm package download the binary (that corresponds to the system) from GitHub release attachments (that correspond to the npm package version).