```bash prepare-swagger path_to_config.yaml path_to_schema.yaml ```
npm install prepare-swagger``bash`
prepare-swagger path_to_config.yaml path_to_schema.yaml
`yaml`
url: https://petstore.swagger.io/v2/swagger.json
request:
# optional headers
headers:
x-sc-lb-hint: default
paths:
# key: search regex, value: replacement
^/pet(/.*): /my_pet$1
__remove:
- path_to_remove
definitions:
# definitions to add
AddDto:
properties:
id:
type: string
required:
- '*' # all properties
# definitions to override
ModifyDto:
properties:
id:
type: string
# properties to remove
__remove:
- key
# specific properties
required:
- id
# definitions to remove
__remove:
- RemoveDto
After yarn build/npm run build command, you can see package-template.[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, each commit and pull request will be built and tested automatically in [@node22] x [macOS, Linux, 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 it to install build toolchain like gcc/llvm, node-gyp or something more.
With GitHub actions, we can easily prebuild a binary for major platforms. And with N-API, we should never be afraid of ABI Compatible.
The other problem is how to deliver prebuild binary to users. Downloading it in postinstall script is a common way that most packages do it right now. The problem with this solution is it introduced many other packages to download binary that has not been used by runtime codes. The other problem is some users may not easily download the binary from GitHub/CDN if they are behind a private network (But in most cases, 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 platforms. And add it to optionalDependencies before releasing 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.
- Install the latest Rust
- Install which fully supported Node-API
- Install
- yarn
- yarn build
- yarn test
And you will see:
`bash
$ ava --verbose
✔ sync function from native code
✔ sleep function from native code (201ms)
─
2 tests passed
✨ Done in 1.12s.
`
Ensure you have set your NPM_TOKEN in the GitHub project setting.
In Settings -> Secrets, add NPM_TOKEN into it.
When you want to release the package:
`bash
npm version [
git push
`
GitHub actions will do the rest job for you.
> WARN: Don't run npm publish` manually.