Repository navigation
Embedding: Distribute official libnode.so/dll/dylib bins #58031
Description
Activity
Hi @RaisinTen, the ticket you referenced is about improving the
libnodeAPI to make it easier to embed (e.g. offer a C API) - however it still requires compiling libnode manually.This ticket is about providing official prebuilt binaries for
libnode- which can be done with the existing C++ API.Correct me if I am wrong but I believe they are different requests?
Hey @alshdavid, the other issue proposes this as the feature for solving the problem:
It would be amazing if Node.js released a libnode library that exported Node.js capabilities and enabled napi access to the host context.
That's the same as distributing prebuilt official libnode binaries, so it makes more sense to track the work for including libnode binaries in the official Node.js releases on that issue.
For a C API, there is this WIP PR #54660. Looks like you're already coordinating with Vladimir on your C entrypoint PR #57846.
Hey @RaisinTen, just a quick one on this subject. I have this GitHub workflow that I run every time Nodejs releases a new version which generates prebuilt binaries for
libnode(I assume the final state would be more complex given the platform support surface of Nodejs).I wanted to raise a PR to start working on adding prebuilt libnode binaries to the Nodejs repo for consideration by the team but it doesn't look like Nodejs is using Github actions to generate binaries. Any chance you could point me at the CI code so I can work on those changes? 🙏
Thanks!
What is the problem this feature will solve?
Currently Node is distributed officially as an executable binary here: https://nodejs.org/dist/v22.15.0/.
For applications that intend to embed libnode, embedders must manually compile and distribute libnode.
There are projects like https://github.com/metacall/libnode that distribute prebuilt copies of libnode however it would be amazing if there was a reliable official source to fetch libnode as it would help with distributing applications that depend on it.
What is the feature you are proposing to solve the problem?
Distribute prebuilt libnode binaries from the Nodejs website. For example:
With a reliable url to fetch libnode, embedders could package/distribute libnode along with their applications or fetch libnode dynamically on the first run of their application.
What alternatives have you considered?
Compiling libnode myself or using unofficial prebuilt packages