Holostep configurator runtime: contract 2.0 ​

The engine-neutral API a Holostep configurator page uses through @holostep-configurators/runtime-client: boot a session, change the scene model, restyle parts, move the camera, drag, assemble, capture and export. The package wins over any note.

Contract 2.0.0 · package sha256 a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e · generated by services/onsite-scripter/scripts/build-contract-docs.mjs; do not edit.

"Spec section N" and the short ids in parentheses (O6, R4, ID8, K47, …) in these pages and in the runtime's messages name the design record a rule comes from. The record is not shipped, and the package is complete without it: read them as provenance, never as something to look up.

Start here ​

API pages ​

1. Basics ​

2. Operations, reports, causes, problems ​

3. Errors ​

4. Boot ​

5. Writers, transactions, session ​

6. Queries, rules and parts ​

7. Collections and shapes ​

8. Materials and textures ​

9. Stage ​

10. Camera ​

11. Input and drag ​

12. Assembly ​

13. Overlays ​

14. Animations ​

15. Frame writer ​

16. Capture, export, AR ​

17. Assets: describe, manifest, validation ​

18. Events ​

19. Info and capabilities ​

20. Labs ​

21. Stored data (vendored; replaces @holo/interfaces) ​

22. Pure helpers (root of the package; run in Node and the fake) ​

23. /math ​

24. /testing ​

Codes ​

Problem codes (ProblemCode) ​

Input-error codes (InputErrorCode) ​

Issue codes (IssueCode) ​