FAQ

Which Three.js version does the skill pack support?

The pack is verified against Three.js 0.185.1, runtime revision 185. Learn what that guarantee covers and how to detect version drift.

The current pack is verified against Three.js 0.185.1, whose runtime revision is 185. Treat that as the supported target, not as a promise that every later release is compatible. Check both the installed package version and THREE.REVISION before using revision-specific API guidance. If either differs, pin or upgrade the project deliberately, then rerun the relevant examples and evidence checks.

Question source
verified-local-failure
Group: compatibility and browser support
Observed
2026-07-12 to 2026-07-16
Answer ownership
/faq/which-threejs-version-does-the-skill-pack-support/
Status: verified
Source references
local:scripts/toolchain-preflight.mjs#THREE_REVISION_MISMATCH

What supported means

The repository manifest pins three to 0.185.1. The rendering skills target r185, and the toolchain preflight requires the imported module to report THREE.REVISION === "185". Supported means that API names, examples, validators, and published evidence contracts were authored and checked against that package and runtime revision.

Check both values. A package manager can resolve a different dependency than expected, and mixed import paths can load more than one Three.js instance.

import * as THREE from 'three/webgpu';

if (THREE.REVISION !== '185') {
  throw new Error(`Expected Three.js r185; received r${THREE.REVISION}`);
}

The repository preflight treats a mismatch as a blocking fact rather than silently applying r185 API literals to another release.

Evidence

Conditions and limitations

  • This is not a compatibility claim for every earlier or later Three.js release.
  • A matching revision does not prove browser support, native WebGPU selection, feature availability, correct pixels, or performance.
  • A newer release may work, but it remains an unverified target until the affected examples and evidence contracts are checked again.
  • Existing projects should pin or upgrade deliberately. They should not change versions solely to make the version check disappear.

Continue with installation, verify the native WebGPU backend, or follow the WebGPURenderer migration guide.

Question provenance

This question comes from a verified local revision-mismatch failure enforced by the repository preflight. It is not presented as a customer question. First observed 2026-07-12; last observed and answer reviewed 2026-07-16.

Relevant skills

Relevant demos and evidence

Sources and correction path