Repository navigation
feat: demonstrate production asset resolution with Three.js - #2
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add two Three.js examples that load the public production RobotExpressive asset through the LoA asset manager: an unbundled page using a CLI-generated asset-resolution.json map, and a Vite page using virtual:loa in remote or local mode. Both use the same pinned manifest, lockfile, scene, and LoadingManager URL modifier.
Use published runtime/SDK/CLI 3.2.0 packages, keep generated maps and binaries out of Git, and document anonymous setup, attribution, local pulling, static builds, and hardware-GPU verification. Add PR, main, manual, and weekly production integration checks with downloadable build artifacts.
Validation: JavaScript typecheck; five integration tests covering production SDK metadata, anonymous CORS/downloads, SHA-256, Three.js parsing, CLI-generated local maps, standalone HTTP routes, and Vite dev/build behavior; all three static builds. Hardware-GPU visual verification remains pending because the Browser plugin has no connected browser.
Closes #1