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
> Template project for writing node packages with napi-rs.
6
6
@@ -14,14 +14,14 @@
14
14
## Install this test package
15
15
16
16
```
17
-
pnpm add @napi-rs/package-template
17
+
pnpm add @napi-rs/ripgrep-napi
18
18
```
19
19
20
20
## Usage
21
21
22
22
### Build
23
23
24
-
After `pnpm 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).
24
+
After `pnpm build` command, you can see `ripgrep-napi.[darwin|win32|linux].node` file in project root. This is the native addon built from [lib.rs](./src/lib.rs).
25
25
26
26
### Test
27
27
@@ -41,7 +41,7 @@ The other problem is how to deliver prebuild `binary` to users. Downloading it i
41
41
42
42
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.
43
43
44
-
`NPM` will choose which native package should download from `registry` automatically. You can see [npm](./npm) dir for details. And you can also run `pnpm add @napi-rs/package-template` to see how it works.
44
+
`NPM` will choose which native package should download from `registry` automatically. You can see [npm](./npm) dir for details. And you can also run `pnpm add @napi-rs/ripgrep-napi` to see how it works.
0 commit comments