Skip to content
Publishing a binding

web-tree-sitter-runtime

0.26.11

Reads Clay source text in the page and on a server.

BrowserNativeCPUOfflineBuilt in

Runs on 2 of 2 nodes

that you can see

Shared

Private

See everything that runs on cloud-nbg1-1

Details · answers, reads, artifact, licence, provenance
Built in

The WebAssembly runtime of tree-sitter, the incremental parser Clay uses to read its own source code.

Runs in
BrowserServer
Any WebAssembly host
Form
WebAssembly, 201 KB
Same answer every timeSame answer
Yes
Network
Never
Licence
MIT
Signed
By Clay, development keyBy Clay, dev key

Who loads it

Clay’s own tools load this binding. Your programs don’t call it, so it never appears in their types.

  • The editor and the compiler's parser wrapper.

Exact bytes and where they came from

Upstream · github.com/tree-sitter/tree-sitter at 0.26.11
Project
https://github.com/tree-sitter/tree-sitter
Version
0.26.11
Commit or revision
Not recorded
Licence
MIT
How it was built
Toolchain
Not recorded
Built by
upstream (tree-sitter)
Built at
2026-11-08T00:00:00.000Z
Memory
Not measured
CPU
Not measured
Source path
packages/compiler/node_modules/web-tree-sitter/web-tree-sitter.wasm
Format
file
  1. Prebuilt wasm shipped in the npm package web-tree-sitter; not rebuilt here.
Signatures · 1, development key

Checked when this page was built, against the trust set.

  • c5878029baeb4574 Clay, development key: valid (ok)
Manifest id
c1f008cb3405da25a3b4d0d4dd469a860211a19ad2024bb9c7e70cf8c937cb39
Status
ok
Loading it from a runner · checkLoadable, with the code

Fetch /v1/manifests/c1f008cb3405da25a3b4d0d4dd469a860211a19ad2024bb9c7e70cf8c937cb39.json, get the artifact bytes by hash, then call checkLoadable(manifest, bytes, policy). It checks the signature against the trusted keys, the revocation list, the fingerprints and sizes, and the policy’s allowed forms and determinism classes, and returns a reason when it refuses. How a runner loads a binding