@looop-games/cli 0.1.29 → 0.1.30
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +9 -0
- package/lib/inject.mjs +3 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -14,6 +14,15 @@ Versions: [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
|
14
14
|
|
|
15
15
|
## [Unreleased]
|
|
16
16
|
|
|
17
|
+
## [0.1.30] - 2026-08-21
|
|
18
|
+
|
|
19
|
+
### Fixed
|
|
20
|
+
- `looop dev` now resolves `three` for a 3D game with **no import map of its
|
|
21
|
+
own** — it maps the bare `three` specifier to the engine's bundled copy, the
|
|
22
|
+
same as the published serve path. Before this, deleting your CDN three import
|
|
23
|
+
map (as engine 0.2.3 tells you to) white-screened the game under `looop dev`,
|
|
24
|
+
because the dev server didn't yet supply `three`. Requires engine 0.2.3+.
|
|
25
|
+
|
|
17
26
|
## [0.1.29] - 2026-08-19
|
|
18
27
|
|
|
19
28
|
### Added
|
package/lib/inject.mjs
CHANGED
|
@@ -42,6 +42,9 @@ const V2_IMPORTS = {
|
|
|
42
42
|
// never white-screens on a node:fs load. Node resolves looop/test via the build
|
|
43
43
|
// register hook (expand.js), which points at the real test.js regardless.
|
|
44
44
|
'looop/test': '/shared/framework/runtime/test-browser.js',
|
|
45
|
+
// three, mapped to the engine's own vendored same-origin copy so a three-backed
|
|
46
|
+
// game needs no import map of its own (kept in sync with serve-import-map.ts).
|
|
47
|
+
three: '/shared/ui/room/vendor/three.js',
|
|
45
48
|
};
|
|
46
49
|
|
|
47
50
|
export function injectHeadTags(html, slug, { identity = DEV_IDENTITY, platformUrl = PLATFORM_URL, toolbox = false, toolboxUrl = TOOLBOX_URL, skeleton = null } = {}) {
|