Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/u-c-s/rusty-jsonwebtoken
A JWT library for node, implemented in Rust (WIP)
https://github.com/u-c-s/rusty-jsonwebtoken
jsonwebtoken jwt napi npm-package rust
Last synced: about 6 hours ago
JSON representation
A JWT library for node, implemented in Rust (WIP)
- Host: GitHub
- URL: https://github.com/u-c-s/rusty-jsonwebtoken
- Owner: U-C-S
- License: mit
- Created: 2022-04-13T14:44:12.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2022-10-11T19:09:35.000Z (about 2 years ago)
- Last Synced: 2024-10-12T14:34:16.283Z (about 1 month ago)
- Topics: jsonwebtoken, jwt, napi, npm-package, rust
- Language: Rust
- Homepage:
- Size: 311 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# `@napi-rs/package-template`
> Template project for writing node package with napi-rs.
# Usage
1. Click __Use this template__.
2. __Clone__ your project.
3. Run `yarn install` to install dependencies.
4. Run `npx napi rename [name]` command under the project folder to rename your package.
## Install this test package
```
yarn add @napi-rs/package-template
```
## Support matrix
### Operating Systems
| | node12 | node14 | node16 |
| ---------------- | ------ | ------ | ------ |
| Windows x64 | ✓ | ✓ | ✓ |
| Windows x32 | ✓ | ✓ | ✓ |
| Windows arm64 | ✓ | ✓ | ✓ |
| macOS x64 | ✓ | ✓ | ✓ |
| macOS arm64 | ✓ | ✓ | ✓ |
| Linux x64 gnu | ✓ | ✓ | ✓ |
| Linux x64 musl | ✓ | ✓ | ✓ |
| Linux arm gnu | ✓ | ✓ | ✓ |
| Linux arm64 gnu | ✓ | ✓ | ✓ |
| Linux arm64 musl | ✓ | ✓ | ✓ |
| Android arm64 | ✓ | ✓ | ✓ |
| Android armv7 | ✓ | ✓ | ✓ |
| FreeBSD x64 | ✓ | ✓ | ✓ |
## Ability
### Build
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](./src/lib.rs).
### Test
With [ava](https://github.com/avajs/ava), run `yarn test/npm run test` to testing native addon. You can also switch to another testing framework if you want.
### CI
With GitHub actions, every commits and pull request will be built and tested automatically in [`node@12`, `node@14`, `@node16`] x [`macOS`, `Linux`, `Windows`] matrix. You will never be afraid of the native addon broken in these platforms.
### Release
Release native package is very difficult in old days. Native packages may ask developers who use its to install `build toolchain` like `gcc/llvm` , `node-gyp` or something more.
With `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](./npm) dir for details. And you can also run `yarn add @napi-rs/package-template` to see how it works.
## Develop requirements
- Install latest `Rust`
- Install `Node.js@10+` which fully supported `Node-API`
- Install `[email protected]`
## Test in local
- 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.
```
## Release package
Ensure you have set you **NPM_TOKEN** in `GitHub` project setting.
In `Settings -> Secrets`, add **NPM_TOKEN** into it.
When you want release package:
```
npm version [ | major | minor | patch | premajor | preminor | prepatch | prerelease [--preid=] | from-git]
git push
```
GitHub actions will do the rest job for you.