Files
zeekay 6a0a3ab088 Every crate names its dependencies itself, and every published crate moves a patch
No crate inherits from the workspace any longer: each manifest holds its
own version, package fields, lints and dependency specs, siblings as a
path and the exact version they publish at. The root keeps members,
exclude, resolver and profiles. Every publishable crate takes a patch
bump so the registry carries manifests that stand alone.

Claude-Session: https://claude.ai/code/session_01JupC8d38f9Lkfz62hvjG2q
2026-10-06 14:44:26 -07:00
..
2026-01-16 12:30:55 -08:00
2026-01-16 12:30:55 -08:00
2026-01-16 12:30:55 -08:00
2026-01-16 12:30:55 -08:00

Running T5 with ML and WASM

Here, we provide two examples of how to run Bert using a ML-compiled WASM binary and runtime.

Vanilla JS and WebWorkers

To build and test the UI made in Vanilla JS and WebWorkers, first we need to build the WASM library:

sh build-lib.sh

This will bundle the library under ./build and we can import it inside our WebWorker like a normal JS module:

import init, { ModelConditionalGeneration, ModelEncoder } from "./build/m.js";

For the quantized version, we need to import the quantized module:

import init, { ModelConditionalGeneration, ModelEncoder } from "./build/m-quantized.js";

The full example can be found under ./index.html. All needed assets are fetched from the web, so no need to download anything. Finally, you can preview the example by running a local HTTP server. For example:

python -m http.server

Then open http://localhost:8000/index.html in your browser.