npm / @pixiv/three-vrm
@pixiv/three-vrm
What changed in @pixiv/three-vrm 2 to 3, from its official release notes, upgrade guides and advisories. Sources checked 2026-11-12.
5 breaking1 new APIs and options3 behavior and defaults5 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@pixiv/three-vrm 313 changes
Breaking changes 4
MToon now respects rimLightingMixFactor; models with a non-default value may show visual differences.
Adds a WebGPU-compatible MToon material via the NodeMaterial system; select it with the materialType option of MToonMaterialLoaderPlugin. Requires Three.js r167 or later.
The default is now false. Set plugin.metaPlugin.needThumbnailImage to true if you use meta.thumbnailImage.
TypeScript 3.9 or earlier is no longer supported; users must update TypeScript.
New APIs and options 1
Adds resetValues to VRMExpressionManager.
Behavior and default changes 3
Warns when a VRM0 morph bind target mesh is not found.
removeUnnecessaryVertices now supports interleaved buffers.
This field might contain materials other than MToonMaterial, namely MToonNodeMaterial.
Fixes and other changes 5
Handles negative node indices (-1) in VRM0.0 humanoid bones.
Texture assignment error handling was improved in the MToon loader.
Error handling was improved for VRM0 import.
Error handling was improved for VRMSpringBoneLoaderPlugin.
MToon shadow casting with SpotLight was fixed.
@pixiv/three-vrm 21 changes
Breaking changes 1
Support for Three.js r136 and prior is dropped.