Files
hyperframes/packages
Miguel Ángel 27a7f37494 fix(lint): recognize Three.js loaded via ESM URL/path imports (#1805)
The missing_three_script rule only treated a bare import from 'three' as
loading Three.js, so ESM imports whose specifier is a URL or path (e.g.
.../+esm CDN builds, esm.sh/three, unpkg three.module.js, or a local
three.module.js) were not recognized. Compositions using THREE. with such
an import got a false blocking error, pushing authors onto the deprecated
UMD global build.

Generalize the module-import detection to count any import/from whose
specifier contains "three" (case-insensitive), matching the existing
loose /three/i treatment of <script src>. Bare 'three', importmap, and
<script src> paths are unchanged; the specifier must still contain
"three", so unrelated imports do not satisfy it.
2026-06-30 11:31:42 -07:00
..
2026-06-29 21:13:39 -07:00
2026-06-29 21:13:39 -07:00
2026-06-29 21:13:39 -07:00
2026-06-29 21:13:39 -07:00
2026-06-29 21:13:39 -07:00
2026-06-29 21:13:39 -07:00
2026-06-16 13:16:09 -04:00
2026-06-29 21:13:39 -07:00
2026-06-29 21:13:39 -07:00