Release evidence / 0.4.0 candidate
Check the work behind the API.
OGJS owns canvas sizing, coordinates, framing, motion, interaction, lifecycle, and export. This page records how the current release candidate reduces application code, how you can repeat its performance measurements, and which checks protect the package.
- Evidence date
- 2026-08-23
- Runtime dependencies
- 0
- Runnable examples
- 61
- Source package
- Code + declarations
Developer adoption
Measured across every example listed in the public catalog.
The authored-code comparison uses the same 61 files before and after the turnkey API pass: 4,574 lines became 4,057. It excludes blank lines, explanatory comments, and fenced browser-test probes.
Release gates
Each command fails the release when its boundary changes.
| Gate | Checks | Run it |
|---|---|---|
| Portable correctness | Types, package build, unit coverage, and browser pixels. | npm run evidence:portable |
| Consumer package | Packed tarball installed into an isolated application. | npm run verify:consumer |
| Framework lifecycle | Angular build plus React, Vue, and Svelte adapter coverage. | npm run verify:angular |
| Language bridge | Java, C#, Go, PHP, and Rust emit the same protocol document. | npm run verify:languages |
| Site discovery | Every built page has crawl metadata and one sitemap URL. | npm run build:site |
Performance method
Device measurements replace generic speed claims.
The performance lab creates a seeded workload, records its node and edge counts, and measures build, rendering, picking, grouping, CPU layout, and the accelerated layout path on your browser. Reports include the viewport and WebGL capabilities needed to interpret the result.
Saved profiles compare only with compatible profiles. Software-rendered GPU results remain labelled as software-rendered, so a CPU result cannot masquerade as a hardware comparison.
Trace a claim
Open the implementation surface that supports each statement.
Package boundary
The npm package carries JavaScript, TypeScript declarations, workers, and required package metadata. The website hosts fonts, icons, imagery, and geographic reference data. Applications choose and host their own visual assets.
OGJS is commercial software. The public site documents the API and runs its examples; the source repository remains private.