Repository navigation
Releases
fourJS 0.1.0 — first public release
fourJS 0.1.0 is the first public release: 24 packages, all at 0.1.0, published under the @danielsimonjr npm scope.
Install
npm install @danielsimonjr/fourjsThe umbrella package @danielsimonjr/fourjs re-exports every subsystem through 26 subpath exports (for example @danielsimonjr/fourjs/scene). Each subsystem is also published on its own as @danielsimonjr/fourjs-<name>.
Requirements
- ESM only. Every package is
"type": "module"and declares norequirecondition.require()fails withERR_PACKAGE_PATH_NOT_EXPORTED. This is intentional. - TypeScript: use
moduleResolutionset tonodenextorbundler. fourJS's own declarations compile cleanly understrictwithskipLibCheck: false. WithskipLibCheck: false, setlibtoesnext, because the@dimforge/rapier*-compatdependencies ship declarations that useSymbol.dispose. Details:docs/COMPATIBILITY.md§0.
Scope of 0.1
This release follows spec §94's 0.1 line: math, scene, time, and basic WebGL rendering, plus the subsystems already built on top of them. Several feature areas are still open and are not part of 0.1.0. Examples are rectangular and clustered lights, shadow cascades and point/spot shadow maps, the GPU morph-target path, storage-buffer bindings in node materials, and bounded JPEG/WebP/AVIF decoding. They are tracked in the repository's TODO.md, and the API around them may still change.
Release readiness
Before publishing, the release went through a rubber-duck review and a consumer-seat dogfood pass. The consumer project lived outside the workspace, installed the staged tarballs, imported all 26 subpaths, typechecked against the shipped declarations, and loaded the ESM entry under Node. Defects fixed as a result:
- The build did not compile:
WebAssemblyandBufferSourcehad no declarations under the DOM-freelib. - A renderer interface (
StandardPipeline) had fallen out of sync with its implementation. examples/gltf-modelrendered an empty canvas: the standard pipeline was never registered.- Development warnings named workspace packages (
@fourjs/*) that do not exist on npm. check-compatfailed on every Windows checkout, and a browser test hid the cause of its own failures.
The full list is in CHANGELOG.md.
Packages
| Package | Version |
|---|---|
@danielsimonjr/fourjs |
0.1.0 |
@danielsimonjr/fourjs-animation |
0.1.0 |
@danielsimonjr/fourjs-assets |
0.1.0 |
@danielsimonjr/fourjs-core |
0.1.0 |
@danielsimonjr/fourjs-diagnostics |
0.1.0 |
@danielsimonjr/fourjs-geometry |
0.1.0 |
@danielsimonjr/fourjs-input |
0.1.0 |
@danielsimonjr/fourjs-materials |
0.1.0 |
@danielsimonjr/fourjs-math |
0.1.0 |
@danielsimonjr/fourjs-motion |
0.1.0 |
@danielsimonjr/fourjs-particles |
0.1.0 |
@danielsimonjr/fourjs-physics |
0.1.0 |
@danielsimonjr/fourjs-physics-box2d |
0.1.0 |
@danielsimonjr/fourjs-physics-rapier |
0.1.0 |
@danielsimonjr/fourjs-physics-soft |
0.1.0 |
@danielsimonjr/fourjs-render |
0.1.0 |
@danielsimonjr/fourjs-render-canvas |
0.1.0 |
@danielsimonjr/fourjs-render-svg |
0.1.0 |
@danielsimonjr/fourjs-render-webgl |
0.1.0 |
@danielsimonjr/fourjs-render-webgpu |
0.1.0 |
@danielsimonjr/fourjs-scene |
0.1.0 |
@danielsimonjr/fourjs-serialization |
0.1.0 |
@danielsimonjr/fourjs-text |
0.1.0 |
@danielsimonjr/fourjs-ui |
0.1.0 |