@nirs4all/datasets-wasm

WASM binding over the nirs4all-datasets acquisition core. Scoped to metadata + small public datasets: it resolves the download contract from the distributable catalog/index.json and computes SHA-256, but does not itself download large files — in the browser, Dataverse CORS is per-instance, there is no real filesystem, and dataset size is bounded (see migration_ABI_C.md §4). The native bindings (Python / R / Octave-MATLAB) do the byte download + caching.

const wasm = require("@nirs4all/datasets-wasm"); // or `import` for the web target
const index = await (await fetch(INDEX_URL)).text();       // catalog/index.json
const contract = JSON.parse(wasm.resolve(index, "corn_eigenvector_nir"));
// contract.files[i].sha256  -> verify a blob you fetched yourself:
const ok = wasm.sha256(new Uint8Array(buf)) === contract.files[0].sha256;

Build the browser package used by nirs4all-web:

wasm-pack build bindings/wasm --release --target web --out-dir pkg --scope nirs4all

Build and test the Node package:

wasm-pack build bindings/wasm --release --target nodejs --out-dir pkg-node --scope nirs4all
node bindings/wasm/tests/node_smoke.cjs

wasm-pack derives the local generated package name from the crate (@nirs4all/nirs4all-datasets-wasm). The release workflow rewrites it to the published npm package name shown above.