You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
node-bindgen is primary used for building native-modules using Rust. However, it assumes that consume of the modules has rust/cargo toolschain installed and expected to use to build modules. We need to enable for non rust users to consume the modules.
In order to do so we should do following
Enhance Nj-cli to publish NPM modules with binaries bundles in. It should have list of rust target that should be included in the published module. For example: [x86_64-apple-darwin, x86_64-unknown-linux-gnu].
When modules are installed, it should only keep binaries that are specific to host
The text was updated successfully, but these errors were encountered:
Regarding your 2nd point, there are at least two ways of doing it:
Bundle the binaries for all platforms in the npm package itself, then post-install just link the relevant one and ignore/discard the rest.
Keep the binaries packaged as github releases, not on the npm package. The npm package will download the relevant binary post install. We get a smaller npm package in exchange for an extra download during package installation.
node-bindgen
is primary used for building native-modules using Rust. However, it assumes that consume of the modules hasrust/cargo
toolschain installed and expected to use to build modules. We need to enable for non rust users to consume the modules.In order to do so we should do following
Nj-cli
to publish NPM modules with binaries bundles in. It should have list of rust target that should be included in the published module. For example:[x86_64-apple-darwin, x86_64-unknown-linux-gnu]
.The text was updated successfully, but these errors were encountered: