@oxidezap/whatsapp-rust-bridge 0.19.0 → 0.20.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +32 -0
- package/dist/index.js +2 -2
- package/dist/whatsapp_rust_bridge.d.ts +158 -59
- package/dist/whatsapp_rust_bridge_bg.wasm +0 -0
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -2,6 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
[](https://www.npmjs.com/package/@oxidezap/whatsapp-rust-bridge)
|
|
4
4
|
[](https://www.npmjs.com/package/@oxidezap/whatsapp-rust-bridge)
|
|
5
|
+
[](https://pkg.pr.new/~/oxidezap/whatsapp-rust-bridge)
|
|
5
6
|
|
|
6
7
|
High-performance WhatsApp utilities powered by Rust and WebAssembly.
|
|
7
8
|
|
|
@@ -15,3 +16,34 @@ High-performance WhatsApp utilities powered by Rust and WebAssembly.
|
|
|
15
16
|
| Audio (waveform, duration) | ✅ |
|
|
16
17
|
| Image (thumbnails, conversion) | ✅ |
|
|
17
18
|
| Sticker Metadata | ✅ |
|
|
19
|
+
|
|
20
|
+
## Preview builds
|
|
21
|
+
|
|
22
|
+
Every commit CI builds and tests — on `main` and on every pull request — then
|
|
23
|
+
uploads that build to
|
|
24
|
+
[pkg.pr.new](https://github.com/stackblitz-labs/pkg.pr.new), installable from a
|
|
25
|
+
URL. Nothing is published to npm, so a fix can be tried before it reaches a
|
|
26
|
+
release:
|
|
27
|
+
|
|
28
|
+
```sh
|
|
29
|
+
# the head of a pull request, following it as new commits land
|
|
30
|
+
npm install https://pkg.pr.new/@oxidezap/whatsapp-rust-bridge@88
|
|
31
|
+
|
|
32
|
+
# one specific commit
|
|
33
|
+
npm install https://pkg.pr.new/@oxidezap/whatsapp-rust-bridge@7ef8db0
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
Every open pull request comments the URL for its own head, and
|
|
37
|
+
[pkg.pr.new/~/oxidezap/whatsapp-rust-bridge](https://pkg.pr.new/~/oxidezap/whatsapp-rust-bridge)
|
|
38
|
+
lists what is available. Two things leave a commit without one. A release
|
|
39
|
+
version bump is not built at all — CI skips a diff that cannot reach the build,
|
|
40
|
+
and that commit is on its way to npm anyway. And the upload does not fail the
|
|
41
|
+
run: pkg.pr.new is not this repository's to keep up, so a green commit with no
|
|
42
|
+
preview means it was unreachable, not that the build was bad.
|
|
43
|
+
|
|
44
|
+
The tarball is the one the run built and tested: the same `bun run build`
|
|
45
|
+
output, packed through the same `prepack` guard a real publish goes through.
|
|
46
|
+
What it is not is a release. Preview builds carry the version
|
|
47
|
+
`0.0.0-preview-<sha>`, which no range written for a real release can match — an
|
|
48
|
+
install is a deliberate pin, and it stays on that commit until you change it.
|
|
49
|
+
They are for trying a change, not for running one.
|