|Jay 29e3855841||9 months ago|
|.github/workflows||10 months ago|
|__test__||9 months ago|
|npm||9 months ago|
|scripts||9 months ago|
|src||9 months ago|
|.gitignore||10 months ago|
|.npmignore||10 months ago|
|Cargo.toml||9 months ago|
|LICENSE||10 months ago|
|README.md||10 months ago|
|build.rs||10 months ago|
|index.d.ts||9 months ago|
|index.js||9 months ago|
|package-lock.json||9 months ago|
|package.json||9 months ago|
|yarn.lock||10 months ago|
Template project for writing node package with napi-rs.
yarn add @napi-rs/package-template
⚠️ Linux musl has not been supported now.
|Linux||macOS||Windows x64 MSVC|
yarn build/npm run build command, you can see
index.[darwin|win32|linux].node file in project root. This is the native addon built from lib.rs.
With ava, run
yarn test/npm run test to testing native addon. You can also switch to another testing framework if you want.
With github actions, every commits and pull request will be built and tested automatically in [
@node14] x [
Windows] matrix. You will never be afraid of the native addon broken in these platforms.
Release native package is very difficult in old days. Native packages may ask developers who use its to install
build toolchains like
node-gyp or something more.
Github actions, we can easily prebuild
binary for major platforms. And with
N-API, we should never afraid of ABI Compatible.
The other problem is how to deliver prebuild
binary to users. Download it in
postinstall script is a common way which most packages do it right now. The problem of this solution is it introduced many other packages to download binary which has not been used by
runtime codes. The other problem is some user may not easily download the binary from
github/CDN if they are behind private network (But in most case, they have a private NPM mirror).
In this package we choose a better way to solve this problem. We release different
npm packages for different platform. And add it to
optionalDependencies before release the
Major package to npm.
NPM will choose which native package should download from
registry automatically. You can see npm dir for details. And you can also run
yarn add @napi-rs/package-template to see how it works.
And you will see:
$ ava --verbose ✔ sync function from native code ✔ sleep function from native code (201ms) ─ 2 tests passed ✨ Done in 1.12s.
Ensure you have set you NPM_TOKEN in
Github project setting.
Settings -> Secrets, add NPM_TOKEN into it.
When you want release package:
yarn version [xxx] git push --follow-tags
Github actions will do the rest job for you.