Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 15 Packages Wiki Activity Actions

wai-quantum for JavaScript: the engine as the npm package @transaction-science/wai-quantum 0.1.0 #534

Merged
dcharlot merged 1 commit from wai/quantum-npm-package into main 2026-10-29 09:20:31 -04:00
Conversation 0 Commits 1 Files changed 9 +467
dcharlot commented 2026-10-29 08:14:38 -04:00
Owner
Copy link

wai/wai-quantum-js/ packs the job service's engine for WebAssembly (wai-web
with its quantum_engine feature, the engine of wai-quantum 0.7.0) and its
bindings as an ES module with its TypeScript declarations and no dependencies,
for a page (init() fetches the .wasm beside the module) or for Node (init is
given its bytes). The package keeps its own version line, as the Python
package does.

  • build.sh: wai-web built for wasm32 with paths remapped (as the views build
    does), wasm-bindgen 0.2.127 (refused if it is not the version wai-web's lock
    file pins), package.json, README and the licence copied, the build refused if
    a local path is left in the bindings or the binary, then packed.
  • test/smoke.mjs, on the package unpacked: a job run with a fresh 32-byte key
    and its receipt verified with this engine's did:key; a forged result that
    does not verify; a program linted and drawn; a refused program with its
    diagnostic code (Q310).
  • test/install.mjs: the README's Node example, run in an empty app that
    installed the tarball with npm, the package found by name and its .wasm by
    the subpath it exports.
  • ci/check.sh runs them all and holds the tarball to the package's allow-list
    (the seven files and nothing else).
  • wai-quantum-js.yml runs ci/check.sh on Linux. wai-quantum-js-release.yml runs
    it on a wai-quantum-cli-v* tag and attaches the tarball and its SHA-256 to the
    release. Nothing is published to a registry from CI.

On the M3 Ultra: the .wasm is 5,928,153 bytes, the tarball 2.26 MB, and every
check passes.

After the merge: the tarball built from main is published by hand, with the owner's two-factor prompt.

Public-name check: clean.

🤖 Generated with Claude Code

wai/wai-quantum-js/ packs the job service's engine for WebAssembly (wai-web with its quantum_engine feature, the engine of wai-quantum 0.7.0) and its bindings as an ES module with its TypeScript declarations and no dependencies, for a page (init() fetches the .wasm beside the module) or for Node (init is given its bytes). The package keeps its own version line, as the Python package does. - build.sh: wai-web built for wasm32 with paths remapped (as the views build does), wasm-bindgen 0.2.127 (refused if it is not the version wai-web's lock file pins), package.json, README and the licence copied, the build refused if a local path is left in the bindings or the binary, then packed. - test/smoke.mjs, on the package unpacked: a job run with a fresh 32-byte key and its receipt verified with this engine's did:key; a forged result that does not verify; a program linted and drawn; a refused program with its diagnostic code (Q310). - test/install.mjs: the README's Node example, run in an empty app that installed the tarball with npm, the package found by name and its .wasm by the subpath it exports. - ci/check.sh runs them all and holds the tarball to the package's allow-list (the seven files and nothing else). - wai-quantum-js.yml runs ci/check.sh on Linux. wai-quantum-js-release.yml runs it on a wai-quantum-cli-v* tag and attaches the tarball and its SHA-256 to the release. Nothing is published to a registry from CI. On the M3 Ultra: the .wasm is 5,928,153 bytes, the tarball 2.26 MB, and every check passes. After the merge: the tarball built from main is published by hand, with the owner's two-factor prompt. Public-name check: clean. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
wai-quantum for JavaScript: the engine as the npm package @transaction-science/wai-quantum 0.1.0
All checks were successful
wai-quantum docs, course and locales / does this change touch it (pull_request) Successful in 6s
Details
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 9s
Details
WAI breaking changes and the conformance runner / WAI breaking · does this change touch WAI (pull_request) Successful in 8s
Details
WAI energy receipts / does this change touch it (pull_request) Successful in 10s
Details
wai-quantum for JavaScript / does this change touch it (pull_request) Successful in 7s
Details
wai-quantum docs, course and locales / the Studio's words in every locale · linux (pull_request) Successful in 37s
Details
WAI breaking changes and the conformance runner / WAI breaking · wire, record and API against main · linux (pull_request) Successful in 1m13s
Details
WAI breaking changes and the conformance runner / WAI breaking and conform · their tests, and the independent verifiers through wai conform · linux (pull_request) Successful in 2m49s
Details
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 3m6s
Details
wai-quantum for JavaScript / javascript · linux (pull_request) Successful in 3m7s
Details
standards workspaces build + test / macOS energy backends (pull_request) Successful in 5m7s
Details
WAI energy receipts / energy receipts · macos (pull_request) Successful in 6m33s
Details
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 8m31s
Details
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Successful in 9m6s
Details
WAI energy receipts / energy receipts · linux (pull_request) Successful in 10m53s
Details
wai-quantum docs, course and locales / the course and the command line's languages · linux (pull_request) Successful in 12m23s
Details
wai-quantum docs, course and locales / every command and snippet in the docs · linux (pull_request) Successful in 1h4m5s
Details
51e89d4e20 
wai/wai-quantum-js/ packs the job service's engine for WebAssembly (wai-web
with its quantum_engine feature, the engine of wai-quantum 0.7.0) and its
bindings as an ES module with its TypeScript declarations and no dependencies,
for a page (init() fetches the .wasm beside the module) or for Node (init is
given its bytes). The package keeps its own version line, as the Python
package does.

- build.sh: wai-web built for wasm32 with paths remapped (as the views build
  does), wasm-bindgen 0.2.127 (refused if it is not the version wai-web's lock
  file pins), package.json, README and the licence copied, the build refused if
  a local path is left in the bindings or the binary, then packed.
- test/smoke.mjs, on the package unpacked: a job run with a fresh 32-byte key
  and its receipt verified with this engine's did:key; a forged result that
  does not verify; a program linted and drawn; a refused program with its
  diagnostic code (Q310).
- test/install.mjs: the README's Node example, run in an empty app that
  installed the tarball with npm, the package found by name and its .wasm by
  the subpath it exports.
- ci/check.sh runs them all and holds the tarball to the package's allow-list
  (the seven files and nothing else).
- wai-quantum-js.yml runs ci/check.sh on Linux. wai-quantum-js-release.yml runs
  it on a wai-quantum-cli-v* tag and attaches the tarball and its SHA-256 to the
  release. Nothing is published to a registry from CI.

On the M3 Ultra: the .wasm is 5,928,153 bytes, the tarball 2.26 MB, and every
check passes.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Transaction-Science/open-standards!534
No description provided.