Releases: Anymfah/paramrig
Release list
@paramrig/web 0.1.2
@paramrig/web@0.1.2 on npm, published from this tag with
provenance; npm audit signatures checks it wherever it is installed.
In the package
- Extract independent SDKs and selective application modules
Modular SDKs 0.1.0
ParamRig engines can now be installed independently. The first coordinated SDK release includes Core, Audio, Sound Labs, browser audio, Vector, Scene and optional React Controls at 0.1.0. Web retains its independent release cycle at 0.1.2.
Install only the package needed by your application, for example npm install @paramrig/audio. Browser adapters and React controls are optional. Vector rendering and canvas-dependent exports require a browser; its contracts, serialization and bindings support Node. Scene uses the host's compatible Three.js installation and can share a host renderer and animation loop.
The attached archives contain the complete application or only Audio, Vector, Scene or Web. These are static web distributions, not native installers. Preserve browser data when updating a deployment.
Validation on revision 0b90ca8a7bcd5d59ad9bcbd326d3ec9b638df3b4: 5,202 tests, typecheck/lint, eight clean consumers, dependency boundaries, portable TypeScript declarations and five selective distributions passed. Registry integrity matches the validated tarballs and all eight clean npm consumers passed. Consumer bundle sizes: Audio with WAV 20,287 bytes gzip; Sound Labs 87,274 bytes gzip. These are bundle measurements, not installation sizes.
The existing dense Audio instrument layout is not yet validated for comfortable phone touch input. The live Scene rendering comparison covers Desk study and its documented modes, supplemented by automated engine tests.
@paramrig/web 0.1.1
@paramrig/web@0.1.1 on npm, published from this tag with
provenance; npm audit signatures checks it wherever it is installed.
In the package
- 0.1.1, the first release the repository publishes by itself
@paramrig/web 0.1.0
@paramrig/web@0.1.0 on npm, the first
published version.
The package is the half of ParamRig that lives in the project being tuned: it exposes a running
development page's design decisions as controls, lets a person tune them in the workbench, and
writes back what they approved as a file in the repository. It is development only, depends on
nothing, and does nothing at all unless a workbench is framing the page. The workbench itself is
not published as a package; it runs from this repository.
This one reached the registry by hand. A trusted publisher on npmjs.com can only be configured for
a package that already exists, so the release workflow ran this tag and failed at its last step.
Every version from 0.1.1 onwards is published by the tag alone, with provenance.