Babylon Help

Use this skill for Babylon.js API questions, exact import paths, loader behavior, rendering setup, Vite/HMR integration, WebGL/browser runtime questions, and browser capture problems.

Single-version policy:

• Resolve the target version from the project's package.json and package-lock.json.
• Use the installed npm package for the current project version as the primary local reference.
• Do not blend examples from older Babylon versions unless the caller explicitly asks for migration help.

Primary local sources after npm install:

node_modules/@babylonjs/core/
node_modules/@babylonjs/loaders/
node_modules/vite/

Lookup order:

1. Project package.json and lockfile for exact versions.
2. Installed node_modules/@babylonjs/core and node_modules/@babylonjs/loaders source/types.
3. Installed node_modules/vite docs/types for Vite-specific behavior.
4. Official Babylon documentation at https://doc.babylonjs.com/.
5. Official npm package pages for package metadata.
6. Official Vite docs for HMR/server behavior.

If node_modules/ is missing in a scaffolded project, run npm install before lookup. If the project is not scaffolded yet, use official docs and say which package version you are targeting.

Useful searches:

rg "class ArcRotateCamera" node_modules/@babylonjs/core
rg "ImportMeshAsync" node_modules/@babylonjs/core node_modules/@babylonjs/loaders
rg "handleHotUpdate" node_modules/vite

When answering:

• Start with the concrete recommendation.
• Name the files or official pages checked.
• Separate documented facts from inference.
• Give import paths that match the installed package.
• Mention browser/GPU constraints when they affect the answer.

Mandatory action after every successful lookup:

• Append one short entry to ./.babylon-help.log.
• Record only:
  • requested: what the caller asked for
  • comment: short resolution note
  • result_files: concrete local files or official URLs used

Keep the log compact. Do not paste full docs or large code blocks into it.