-
The `README.md` for [`prebuild-install`](https://github.com/prebuild/prebuild-install) suggest migrating to `prebuildify` where, instead of publishing native binaries to the GitHub release, they are i…
-
### Feature Request:
Replace `prebuild-install` with [prebuildify](https://github.com/prebuild/prebuildify)
### Motivation:
`prebuildify` ships prebuilt binaries inside the npm package in lieu of sto…
-
Hi,
I've made a fork where I switched to using prebuildify to include the node binaries for each platform. It's been useful for us since we don't have to an run install on a specific platform.
W…
-
The latest Node.js bindings use prebuildify, but the package published to npm is published without any prebuilds, it should be published with prebuilds, see https://github.com/tree-sitter/workflows/bl…
-
Use **prebuildify** to create the pre builds of the module for different architecture and os.
-
### Problem
I see there's been some changes recently relating to GH Actions CI and publishing. Do you have a working example of how to publish a tree-sitter grammar on npm?
Here is my grammar:
…
-
Hello,
I am using the library with electron I am using other native libraries too.
All the others are moving toward NAPI and you successfully made that transition.
Also they are using [nodGypBui…
-
## Summary
Use [`prebuildify`](https://github.com/prebuild/prebuildify) to bundle native code in the NPM package, instead of `prebuild`. `prebuildify` bundles prebuilt native code in the node_modul…
ghost updated
2 years ago
-
We use prebuildify to prebuild for the target environments that we use and execute it something like this:
```sh
prebuildify -t 18.20.3 -t 20.13.1 -t electron@29.4.0 -t electron@30.0.6
```
With …
-
## Summary
`prebuild-install` is recommending:
> **Instead of [`prebuild`](https://github.com/prebuild/prebuild) paired with [`prebuild-install`](https://github.com/prebuild/prebuild-install…