No description
Find a file
2020-02-19 17:45:57 +08:00
.github/workflows build: enhance the build pipeline 2020-02-19 17:45:57 +08:00
build feat: upgrade to std-future 2020-02-18 21:09:17 +08:00
napi build: enhance the build pipeline 2020-02-19 17:45:57 +08:00
scripts build: enhance the build pipeline 2020-02-19 17:45:57 +08:00
test_module build: enhance the build pipeline 2020-02-19 17:45:57 +08:00
.editorconfig init 2018-04-28 16:26:38 +08:00
.gitignore feat: upgrade to std-future 2020-02-18 21:09:17 +08:00
.yarnrc feat: upgrade to std-future 2020-02-18 21:09:17 +08:00
Cargo.toml feat: upgrade to std-future 2020-02-18 21:09:17 +08:00
FUNDING.yml chore: add FUNDING.yml 2020-02-19 00:01:47 +08:00
LICENSE chore: add license 2018-05-01 14:17:51 +08:00
package.json build: enhance the build pipeline 2020-02-19 17:45:57 +08:00
README.md build: enhance the build pipeline 2020-02-19 17:45:57 +08:00
rustfmt.toml Implement buffer 2019-05-23 19:28:51 +08:00
yarn.lock build: enhance the build pipeline 2020-02-19 17:45:57 +08:00

napi-rs

This project was initialized from xray

Platform Support

Operating Systems

Linux macOS Windows x64 MSVC

Python

Node10 Node 12 Node13

A minimal library for building compiled Node add-ons in Rust.

This library depends on N-API and requires Node 8.9 or later. It is still pretty raw and has not been tested in a production setting.

One nice feature is that this crate allows you to build add-ons purely with the Rust toolchain and without involving node-gyp.

Building

This repository is a Cargo crate. Any napi-based add-on should contain Cargo.toml to make it a Cargo crate.

In your Cargo.toml you need to set the crate-type to "cdylib" so that cargo builds a C-style shared library that can be dynamically loaded by the Node executable. You'll also need to add this crate as a dependency.

[lib]
crate-type = ["cdylib"]

[dependencies]
napi-rs = "0.1"

[build-dependencies]
napi-build = "0.1"

And create build.rs in your own project:

// build.rs
extern crate napi_build;

fn main() {
  napi_build::setup();
}

So far, the napi build script has only been tested on macOS Linux and Windows x64 MSVC.

See the included test_module for an example add-on.

Run cargo build to produce the Dynamic lib file. And install the napi-rs to help you copy Dynamic lib file to .node file in case you can require it in your program.


{
  "package": "your pkg",
  "dependencies": {
    "napi-rs": "^0.1"
  },
  "scripts": {
    "build": "cargo build && napi",
    "build-release": "cargo build --release && napi --release"
  }
}

Then you can require your native binding:

require('./target/debug|release/[module_name].node')

The module_name would be your package name in your Cargo.toml.

xxx => ./target/debug|release/xxx.node

xxx-yyy => ./target/debug|release/xxx_yyy.node

You can also copy Dynamic lib file to an appointed location:

napi [--release] .
napi [--release] ./mylib
napi [--release] ./mylib.node

Testing

Because libraries that depend on this crate must be loaded into a Node executable in order to resolve symbols, all tests are written in JavaScript in the test_module subdirectory.

To run tests:

cd test_module
npm run build
npm test