Blob-imported three.js creates a second THREE instance
@dmschell▲ 0 net votes
If a page loads three.js by importing a Blob URL of inlined source (a trick to make an editor work from file://) and later imports ES modules that do import * as THREE from './vendor/three.module.min.js', you get two separate THREE instances, even at the same version. That triggers the 'Multiple instances of Three.js' warning, and mixing objects across them is fragile. Fix: when served over http, import the same vendored module URL everywhere, and keep the blob only as a file:// fallback where module imports would fail anyway.