@stll/anonymize-wasm 2.5.0 → 2.6.1

package/README.md

@@ -36,7 +36,7 @@ const pipeline = await loadPipeline(
 );
 ```
 
-With Vite, register the helper plugin so the wasm binary, WASI worker, and
+With Vite, register the helper plugin so the wasm binary, ESM glue, and
 `.stlanonpkg` assets survive both dependency pre-bundling (dev) and a
 production `vite build` (the plugin emits the `native/` assets and rewrites the
 runtime asset base to point at them):
@@ -49,8 +49,8 @@ import stllAnonymizeWasm from "@stll/anonymize-wasm/vite";
 By default the plugin emits every bundled prepared package into your build. The
 full-dictionary default package alone is large (~20 MB), plus the per-language
 `cs`, `de`, and `en` variants. If your app only needs some of them, restrict the
-emitted packages with the `packages` option (the wasm binary, glue, and workers
-are always emitted):
+emitted packages with the `packages` option (the wasm binary and glue are
+always emitted):
 
 ```ts
 // Emit only the Czech scoped package.
@@ -80,34 +80,25 @@ app actually loads, or load your own package bytes through `loadPipeline`.
 ## Notes
 
 - Same redaction core as `@stll/anonymize`, running in WebAssembly.
-- The binding targets `wasm32-wasip1-threads` (shared memory), so it needs a
-  cross-origin-isolated context (`SharedArrayBuffer`) in the browser.
+- The binding targets single-thread `wasm32-unknown-unknown`. It runs in ordinary
+  browser contexts without `SharedArrayBuffer`, Web Workers, COOP, or COEP.
 
 ## Third-party licenses
 
-The shipped browser WASI glue (`dist/native/index.wasi-browser.js` and
-`dist/native/wasi-worker-browser.mjs`) is bundled at build time and inlines the
-following MIT-licensed runtime so it is self-contained for consumer bundlers:
-
-- `@napi-rs/wasm-runtime` (MIT) — Copyright (c) napi-rs authors —
-  https://github.com/napi-rs/napi-rs
-- `@tybys/wasm-util` (MIT) — Copyright (c) toyobayashi —
-  https://github.com/toyobayashi/wasm-util
-
-Both are distributed under the MIT License; the full license text is available
-in each project's repository.
+See the package's `LICENSE` and the repository root `ATTRIBUTION.md` for
+dependency attribution.
 
 ## Building from source
 
-The wasm binding is generated by napi-rs and is not checked in:
+The wasm binding is generated by wasm-bindgen and is not checked in:
 
 ```bash
 cd packages/anonymize
-bun run build:native-wasm   # needs the wasm32-wasip1-threads Rust target
+bun run build:native-wasm   # needs the wasm32-unknown-unknown Rust target
 bun run build               # tsdown + native node binding
 bun run build:wasm-assets   # copy glue + build compressed packages into wasm/dist/native
 ```
 
-The `wasm32-wasip1-threads` target is pinned in `rust-toolchain.toml`, so
+The `wasm32-unknown-unknown` target is pinned in `rust-toolchain.toml`, so
 `rustup` installs it automatically; with a non-rustup toolchain run
-`rustup target add wasm32-wasip1-threads` first.
+`rustup target add wasm32-unknown-unknown` first.