min-repro-builder

To create a minimal reproducible bug environment, scaffold a tiny, shareable scene within your repo that isolates the issue. This approach reuses existing src assets and scenes, avoiding new files while enabling fast debugging sessions across audio, rendering, and asset-loading.

The best way to isolate rendering and audio bugs is to scaffold a minimal reproduction route using existing assets. By launching a tiny scene via npm run dev, you can observe the specific issue in a controlled environment and log the output for analysis.

To structure logs when reproducing JavaScript bugs, use a dedicated logger module like logger.js within your minimal scene. This provides structured observability during the repro workflow, making the debug route's output easier to analyze for the specific issue.

Yes, you need existing src assets and a minimal scene to scaffold a reproducible environment. The process leverages your current assets and scenes to avoid introducing new files, ensuring the reproduced bug accurately reflects the original codebase conditions.

Yes, you can reproduce state and asset-loading issues without adding new files by reusing existing src/assets. The scaffolding process creates a tiny, shareable scene that leverages current resources to isolate the bug for quick debugging.

To launch a debug route to test a reproduced bug, run npm run dev after initializing the minimal scene. This starts the local development server and opens the isolated reproduction route so you can verify the audio or rendering issue.