@iwsdk/cli 1.2.0-rc.0 → 1.2.0-rc.1
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/README.md +40 -13
- package/dist/agent-guidance/files/.agents/skills/iwsdk-build-model/SKILL.md +1 -1
- package/dist/agent-guidance/files/.agents/skills/iwsdk-compose-scene/SKILL.md +1 -1
- package/dist/agent-guidance/files/.agents/skills/iwsdk-debug/SKILL.md +1 -1
- package/dist/agent-guidance/files/.agents/skills/iwsdk-depth-occlusion/SKILL.md +1 -1
- package/dist/agent-guidance/files/.agents/skills/iwsdk-dev/SKILL.md +1 -1
- package/dist/agent-guidance/files/.agents/skills/iwsdk-dev/references/api-reference.md +2 -1
- package/dist/agent-guidance/files/.agents/skills/iwsdk-dev/references/headless-rendering.md +15 -1
- package/dist/agent-guidance/files/.agents/skills/iwsdk-dev/references/iterate.md +7 -3
- package/dist/agent-guidance/files/.agents/skills/iwsdk-glasses-test/SKILL.md +1 -1
- package/dist/agent-guidance/files/.agents/skills/iwsdk-grab/SKILL.md +1 -1
- package/dist/agent-guidance/files/.agents/skills/iwsdk-hosting/SKILL.md +3 -2
- package/dist/agent-guidance/files/.agents/skills/iwsdk-native-xr-test/SKILL.md +1 -1
- package/dist/agent-guidance/files/.agents/skills/iwsdk-offline/SKILL.md +217 -0
- package/dist/agent-guidance/files/.agents/skills/iwsdk-offline/assets/offline.ts.template +99 -0
- package/dist/agent-guidance/files/.agents/skills/iwsdk-offline/assets/sw.js.template +241 -0
- package/dist/agent-guidance/files/.agents/skills/iwsdk-offline/assets/write-service-worker.mjs.template +72 -0
- package/dist/agent-guidance/files/.agents/skills/iwsdk-offline/references/build-step.md +71 -0
- package/dist/agent-guidance/files/.agents/skills/iwsdk-offline/references/page.md +70 -0
- package/dist/agent-guidance/files/.agents/skills/iwsdk-offline/references/service-worker.md +107 -0
- package/dist/agent-guidance/files/.agents/skills/iwsdk-offline/references/testing.md +57 -0
- package/dist/agent-guidance/files/.agents/skills/iwsdk-physics/SKILL.md +1 -1
- package/dist/agent-guidance/files/.agents/skills/iwsdk-physics/references/tuning-and-config.md +1 -0
- package/dist/agent-guidance/files/.agents/skills/iwsdk-physics/references/workflows.md +9 -3
- package/dist/agent-guidance/files/.agents/skills/iwsdk-pwa-packaging/SKILL.md +13 -2
- package/dist/agent-guidance/files/.agents/skills/iwsdk-pwa-packaging/references/manifest-and-icons.md +1 -1
- package/dist/agent-guidance/files/.agents/skills/iwsdk-pwa-packaging/references/troubleshooting.md +30 -0
- package/dist/agent-guidance/files/.agents/skills/iwsdk-ray/SKILL.md +1 -1
- package/dist/agent-guidance/files/.agents/skills/iwsdk-ui/SKILL.md +12 -5
- package/dist/agent-guidance/files/.agents/skills/iwsdk-upgrade/SKILL.md +1 -1
- package/dist/agent-guidance/files/.claude/agents/iwsdk-project-code-reviewer.md +1 -1
- package/dist/agent-guidance/files/.claude/rules/assets-and-manifest.md +1 -1
- package/dist/agent-guidance/files/.claude/rules/ecs-api.md +1 -1
- package/dist/agent-guidance/files/.claude/rules/scene-json.md +1 -1
- package/dist/agent-guidance/files/.claude/rules/uikitml.md +1 -1
- package/dist/agent-guidance/files/.claude/settings.json +1 -0
- package/dist/agent-guidance/files/.claude/skills/iwsdk-build-model/SKILL.md +1 -1
- package/dist/agent-guidance/files/.claude/skills/iwsdk-compose-scene/SKILL.md +1 -1
- package/dist/agent-guidance/files/.claude/skills/iwsdk-debug/SKILL.md +1 -1
- package/dist/agent-guidance/files/.claude/skills/iwsdk-depth-occlusion/SKILL.md +1 -1
- package/dist/agent-guidance/files/.claude/skills/iwsdk-dev/SKILL.md +1 -1
- package/dist/agent-guidance/files/.claude/skills/iwsdk-dev/references/api-reference.md +2 -1
- package/dist/agent-guidance/files/.claude/skills/iwsdk-dev/references/headless-rendering.md +15 -1
- package/dist/agent-guidance/files/.claude/skills/iwsdk-dev/references/iterate.md +7 -3
- package/dist/agent-guidance/files/.claude/skills/iwsdk-glasses-test/SKILL.md +1 -1
- package/dist/agent-guidance/files/.claude/skills/iwsdk-grab/SKILL.md +1 -1
- package/dist/agent-guidance/files/.claude/skills/iwsdk-hosting/SKILL.md +3 -2
- package/dist/agent-guidance/files/.claude/skills/iwsdk-native-xr-test/SKILL.md +1 -1
- package/dist/agent-guidance/files/.claude/skills/iwsdk-offline/SKILL.md +217 -0
- package/dist/agent-guidance/files/.claude/skills/iwsdk-offline/assets/offline.ts.template +99 -0
- package/dist/agent-guidance/files/.claude/skills/iwsdk-offline/assets/sw.js.template +241 -0
- package/dist/agent-guidance/files/.claude/skills/iwsdk-offline/assets/write-service-worker.mjs.template +72 -0
- package/dist/agent-guidance/files/.claude/skills/iwsdk-offline/references/build-step.md +71 -0
- package/dist/agent-guidance/files/.claude/skills/iwsdk-offline/references/page.md +70 -0
- package/dist/agent-guidance/files/.claude/skills/iwsdk-offline/references/service-worker.md +107 -0
- package/dist/agent-guidance/files/.claude/skills/iwsdk-offline/references/testing.md +57 -0
- package/dist/agent-guidance/files/.claude/skills/iwsdk-physics/SKILL.md +1 -1
- package/dist/agent-guidance/files/.claude/skills/iwsdk-physics/references/tuning-and-config.md +1 -0
- package/dist/agent-guidance/files/.claude/skills/iwsdk-physics/references/workflows.md +9 -3
- package/dist/agent-guidance/files/.claude/skills/iwsdk-pwa-packaging/SKILL.md +13 -2
- package/dist/agent-guidance/files/.claude/skills/iwsdk-pwa-packaging/references/manifest-and-icons.md +1 -1
- package/dist/agent-guidance/files/.claude/skills/iwsdk-pwa-packaging/references/troubleshooting.md +30 -0
- package/dist/agent-guidance/files/.claude/skills/iwsdk-ray/SKILL.md +1 -1
- package/dist/agent-guidance/files/.claude/skills/iwsdk-ui/SKILL.md +12 -5
- package/dist/agent-guidance/files/.claude/skills/iwsdk-upgrade/SKILL.md +1 -1
- package/dist/agent-guidance/files/.cursor/rules/assets-and-manifest.mdc +1 -1
- package/dist/agent-guidance/files/.cursor/rules/ecs-api.mdc +1 -1
- package/dist/agent-guidance/files/.cursor/rules/scene-json.mdc +1 -1
- package/dist/agent-guidance/files/.cursor/rules/uikitml.mdc +1 -1
- package/dist/agent-guidance/files/.github/instructions/assets-and-manifest.instructions.md +1 -1
- package/dist/agent-guidance/files/.github/instructions/ecs-api.instructions.md +1 -1
- package/dist/agent-guidance/files/.github/instructions/scene-json.instructions.md +1 -1
- package/dist/agent-guidance/files/.github/instructions/uikitml.instructions.md +1 -1
- package/dist/agent-guidance/files/AGENTS.md +1 -1
- package/dist/agent-guidance/files/public/scenes/AGENTS.md +1 -1
- package/dist/agent-guidance/files/public/ui/AGENTS.md +1 -1
- package/dist/agent-guidance/files/src/AGENTS.md +1 -1
- package/dist/agent-guidance/manifest.json +111 -11
- package/dist/agent-guidance.d.ts +31 -4
- package/dist/agent-guidance.d.ts.map +1 -1
- package/dist/agent-guidance.js +269 -60
- package/dist/agent-guidance.js.map +1 -1
- package/dist/cli.js +1128 -131
- package/dist/cli.js.map +1 -1
- package/dist/commands/upgrade.d.ts +87 -0
- package/dist/commands/upgrade.d.ts.map +1 -1
- package/dist/guidance-refresh.d.ts +23 -3
- package/dist/guidance-refresh.d.ts.map +1 -1
- package/dist/help.d.ts.map +1 -1
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +1128 -131
- package/dist/index.js.map +1 -1
- package/dist/metavr-telemetry.d.ts +6 -0
- package/dist/metavr-telemetry.d.ts.map +1 -1
- package/dist/package-manager.d.ts +6 -0
- package/dist/package-manager.d.ts.map +1 -1
- package/dist/release-notes.json +132 -0
- package/dist/version.d.ts +1 -1
- package/package.json +1 -1
|
@@ -4,5 +4,11 @@
|
|
|
4
4
|
* This source code is licensed under the MIT license found in the
|
|
5
5
|
* LICENSE file in the root directory of this source tree.
|
|
6
6
|
*/
|
|
7
|
+
/**
|
|
8
|
+
* Starts up to MAX_RUNNING of the events still waiting and drops the rest.
|
|
9
|
+
* Runs when the process exits, so a burst at the end neither floods the
|
|
10
|
+
* machine nor keeps the process alive.
|
|
11
|
+
*/
|
|
12
|
+
export declare function flushQueuedTelemetry(): void;
|
|
7
13
|
export declare function reportToolCall(toolName: string, success: boolean, durationMs: number, error?: string, sessionId?: string, clientVersion?: string): void;
|
|
8
14
|
//# sourceMappingURL=metavr-telemetry.d.ts.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"metavr-telemetry.d.ts","sourceRoot":"","sources":["../src/metavr-telemetry.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;
|
|
1
|
+
{"version":3,"file":"metavr-telemetry.d.ts","sourceRoot":"","sources":["../src/metavr-telemetry.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AA6DH;;;;GAIG;AACH,wBAAgB,oBAAoB,IAAI,IAAI,CAM3C;AAuBD,wBAAgB,cAAc,CAC5B,QAAQ,EAAE,MAAM,EAChB,OAAO,EAAE,OAAO,EAChB,UAAU,EAAE,MAAM,EAClB,KAAK,CAAC,EAAE,MAAM,EACd,SAAS,CAAC,EAAE,MAAM,EAClB,aAAa,CAAC,EAAE,MAAM,GACrB,IAAI,CAoBN"}
|
|
@@ -19,6 +19,12 @@ export interface PackageManagerInfo {
|
|
|
19
19
|
* field or a pnpm workspace decides. Stops at the repository root.
|
|
20
20
|
*/
|
|
21
21
|
export declare function findPackageManager(projectRoot: string): PackageManagerInfo;
|
|
22
|
+
/**
|
|
23
|
+
* True when the project installs with Yarn 2 or later, which takes its
|
|
24
|
+
* registry from .yarnrc.yml rather than .npmrc: its `packageManager` field
|
|
25
|
+
* says so, or, without one, it has a .yarnrc.yml or a Yarn 2+ lockfile.
|
|
26
|
+
*/
|
|
27
|
+
export declare function usesYarnBerry(projectRoot: string, info?: PackageManagerInfo): boolean;
|
|
22
28
|
/**
|
|
23
29
|
* The @iwsdk/core version the lockfile resolves for this project, or null
|
|
24
30
|
* when there is no lockfile this can read. Handles workspace lockfiles, where
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"package-manager.d.ts","sourceRoot":"","sources":["../src/package-manager.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAKH,MAAM,MAAM,kBAAkB,GAAG,KAAK,GAAG,MAAM,GAAG,MAAM,GAAG,KAAK,CAAC;AAEjE,MAAM,WAAW,kBAAkB;IACjC,IAAI,EAAE,kBAAkB,CAAC;IACzB,4EAA4E;IAC5E,IAAI,EAAE,MAAM,CAAC;IACb,4CAA4C;IAC5C,QAAQ,EAAE,MAAM,GAAG,IAAI,CAAC;CACzB;
|
|
1
|
+
{"version":3,"file":"package-manager.d.ts","sourceRoot":"","sources":["../src/package-manager.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAKH,MAAM,MAAM,kBAAkB,GAAG,KAAK,GAAG,MAAM,GAAG,MAAM,GAAG,KAAK,CAAC;AAEjE,MAAM,WAAW,kBAAkB;IACjC,IAAI,EAAE,kBAAkB,CAAC;IACzB,4EAA4E;IAC5E,IAAI,EAAE,MAAM,CAAC;IACb,4CAA4C;IAC5C,QAAQ,EAAE,MAAM,GAAG,IAAI,CAAC;CACzB;AAqFD;;;;;GAKG;AACH,wBAAgB,kBAAkB,CAAC,WAAW,EAAE,MAAM,GAAG,kBAAkB,CAiC1E;AAED;;;;GAIG;AACH,wBAAgB,aAAa,CAC3B,WAAW,EAAE,MAAM,EACnB,IAAI,GAAE,kBAAoD,GACzD,OAAO,CA2BT;AAED;;;;GAIG;AACH,wBAAgB,qBAAqB,CAAC,WAAW,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAuExE"}
|
package/dist/release-notes.json
CHANGED
|
@@ -1,6 +1,32 @@
|
|
|
1
1
|
{
|
|
2
2
|
"format": 1,
|
|
3
3
|
"entries": [
|
|
4
|
+
{
|
|
5
|
+
"version": "1.2.0-rc.1",
|
|
6
|
+
"kind": "patch",
|
|
7
|
+
"text": "`iwsdk dev up` and `dev restart` no longer re-create coding-agent guidance you removed. In 1.2.0-rc.0 every start put back deleted skills and `Skill(iwsdk-*)` permissions, a deleted `AGENTS.md`, and the managed block and `@AGENTS.md` import in a replaced `AGENTS.md` or `CLAUDE.md`. They now update only the guidance a project already has and nobody edited, and replace retired guidance whole: an unedited skill or file that a release renamed or retired is removed only together with writing its successors, and each successor gets the retired skill's permission if it had one. A 0.4 or 0.5 app gets `iwsdk-dev` for `iwsdk-planner`, Cursor and Copilot guidance for the single files 0.4 wrote, and an `AGENTS.md` block for the guidance its `CLAUDE.md` held. Apart from that they never add a skill, file, block, import or permission the project lacks, whether you removed it or it is new in the installed release; when they refresh, the notice lists the skills and files left out. The guidance manifest in `@iwsdk/core` now names what replaces each retired unit. `iwsdk agents sync` and `iwsdk upgrade` still install the full set, and `iwsdk agents check` still reports what is missing.",
|
|
8
|
+
"packages": [
|
|
9
|
+
"@iwsdk/cli",
|
|
10
|
+
"@iwsdk/core"
|
|
11
|
+
]
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"version": "1.2.0-rc.1",
|
|
15
|
+
"kind": "patch",
|
|
16
|
+
"text": "MetaVR telemetry no longer starts one process per command with nothing waiting for it. At most four MetaVR processes run at once and further events wait their turn, so a caller that issues commands quickly (a check script calling `runCli` in a loop, an agent driving the dev server) cannot pile up hundreds of Node processes; 600 rapid commands used to leave about 600 running, now at most four. Events beyond 1000 waiting are dropped, session and error events from the dev server go ahead of waiting tool calls, and on exit a few waiting events are started and the rest dropped. A single command reports exactly as before.",
|
|
17
|
+
"packages": [
|
|
18
|
+
"@iwsdk/cli",
|
|
19
|
+
"@iwsdk/vite-plugin-dev"
|
|
20
|
+
]
|
|
21
|
+
},
|
|
22
|
+
{
|
|
23
|
+
"version": "1.2.0-rc.1",
|
|
24
|
+
"kind": "patch",
|
|
25
|
+
"text": "`iwsdk upgrade` aligns `three` before installing and checks the registry before changing anything. With `--no-install`, or when the install failed, it left the `three` alias, its override and `@types/three` at the old release, so the suggested `npm install` left two Three.js type trees and `tsc` failed. When the registry did not have the release yet, as with a lagging mirror, it changed `package.json` and then failed with ETARGET. Before it writes anything, it now asks the registry the install will use, with the npm or Yarn settings the install reads, for every `@iwsdk/*` package it upgrades, and aligns `three` with the Three.js version that the new `@iwsdk/core` there depends on. When a package is missing it stops with nothing changed (error code `release_not_on_registry`); when the registry cannot be asked, as offline (unless npm's cache has the release) or without npm, it says why, upgrades anyway and aligns `three` after the install, as before. `--dry-run` lists the Three.js changes.",
|
|
26
|
+
"packages": [
|
|
27
|
+
"@iwsdk/cli"
|
|
28
|
+
]
|
|
29
|
+
},
|
|
4
30
|
{
|
|
5
31
|
"version": "1.2.0-rc.0",
|
|
6
32
|
"kind": "minor",
|
|
@@ -459,6 +485,96 @@
|
|
|
459
485
|
"@iwsdk/xr-input"
|
|
460
486
|
]
|
|
461
487
|
},
|
|
488
|
+
{
|
|
489
|
+
"version": "1.2.0-rc.1",
|
|
490
|
+
"kind": "patch",
|
|
491
|
+
"text": "Removing the grabbable component that created a held entity's grab handle (`OneHandGrabbable`, `TwoHandsGrabbable` or `DistanceGrabbable`) now ends the grab. The object stops following the hand right away, and `GrabSystem` removes `Grabbed` on its next update, as it does when the hand lets go or `GrabSystem.forceRelease()` is called, so `Grabbed` release handlers run and queries that exclude `Grabbed` match the entity again. Only that component ends the grab: an entity with several grabbable components has one handle, and removing a component that didn't create it leaves the grab alone. In 1.2.0-rc.0, `Grabbed` stayed on the entity until a grabbable component was added back, even after the hand let go or `GrabSystem.forceRelease()` was called.\n\nRemoving a grabbable component also detaches its handle from the object's pointer events now. In 1.2.0-rc.0 the old handle kept capturing presses on the object and stopping them from propagating after the object was no longer grabbable, and once a grabbable was added back, letting go of a distance grab could snap the object back to where the grab started.",
|
|
492
|
+
"packages": [
|
|
493
|
+
"@iwsdk/core"
|
|
494
|
+
]
|
|
495
|
+
},
|
|
496
|
+
{
|
|
497
|
+
"version": "1.2.0-rc.1",
|
|
498
|
+
"kind": "patch",
|
|
499
|
+
"text": "Controller squeeze grabs now work next to and on pokeable objects. A squeeze used to do nothing while a `PokeInteractable` was within touch range of the controller tip (about 15 cm), for example a keycard inside a pokeable drawer or a climbing hold under a HUD panel. On an entity with both `OneHandGrabbable` and `PokeInteractable`, the controller tip's poke grabbed the object as it arrived, and that grab never let go. Now a squeeze grabs whatever the grab sphere touches and keeps it until the squeeze ends, and a poke presses an entity (`Pressed`, `click`) without grabbing it. A hand pinch also grabs a pokeable grabbable while the fingertip presses it, and an object held by a pinch keeps following the hand while the fingertip presses something.\n\nA squeeze or a hand pinch that grabs something interrupts a poke press in progress, as a browser cancels a touch: the poked object gets `pointercancel` and `pointerleave` instead of `pointerup` and `click`, so the poke no longer keeps it `Pressed` (or UIKit-active) and doesn't click it, and the tip has to move more than 2 cm away from every pokeable before it hovers or presses again. While a squeeze holds a grab, the tip doesn't poke or hover, so a pokeable it was hovering gets `pointerleave` and loses `Hovered` as the grab starts. A squeeze grab also ends when the input source stops reporting the squeeze, for example when the controller is put down mid-squeeze and a tracked hand takes over, instead of keeping that hand locked on the grab.\n\nBehavior change: a poke no longer moves a grabbable. A fingertip or controller tip used to grab a grabbable that is `PokeInteractable` (or part of one) and push it along until the tip lifted off, so a `OneHandGrabbable` limited to one axis worked as a fingertip slider, lever or drawer. Now such an object moves only while a squeeze or pinch holds it. For a control the fingertip should drag, make it `PokeInteractable` rather than grabbable and set its value from its pointer events, for example from `event.point` while it is pressed, and call `setPointerCapture(event.pointerId)` on its `object3D` in its `pointerdown` listener so the press survives the fingertip sliding off it.\n\nBecause a poke no longer grabs, a poke on a grabbable that isn't pokeable itself reaches its pokeable ancestor: poking a keycard parented under a pokeable drawer presses the drawer, as poking any other part of the drawer does. Add `PokeInteractable` to the keycard if it should take the poke itself.\n\n`@iwsdk/core` now needs `@pmndrs/handle` 6.6.28 or later, the first release with the handle `filter` option this relies on.",
|
|
500
|
+
"packages": [
|
|
501
|
+
"@iwsdk/core",
|
|
502
|
+
"@iwsdk/xr-input"
|
|
503
|
+
]
|
|
504
|
+
},
|
|
505
|
+
{
|
|
506
|
+
"version": "1.2.0-rc.1",
|
|
507
|
+
"kind": "patch",
|
|
508
|
+
"text": "Grabbing a dynamic physics body no longer flings its neighbours or launches it on release. A held body is now kinematic and moves evenly across every physics substep; before, a frame that ran several substeps (as slow emulator frames do) overshot the hand each time and could diverge to positions kilometres away. A hand pose jump faster than a hand can move, such as an emulator controller teleport, now moves the held body without sweeping it through its neighbours. On release, the body becomes dynamic again with the hand's smoothed velocity, capped at 10 m/s. The generated physics guidance describes the new behavior.",
|
|
509
|
+
"packages": [
|
|
510
|
+
"@iwsdk/core"
|
|
511
|
+
]
|
|
512
|
+
},
|
|
513
|
+
{
|
|
514
|
+
"version": "1.2.0-rc.1",
|
|
515
|
+
"kind": "patch",
|
|
516
|
+
"text": "The `iwsdk-offline` skill's service worker now takes over only while the asking page is the app's only open page, so a second tab in an XR session is never moved onto a new release; it keeps the other hand's controller model along with the first, and pins the starter's stock models on jsDelivr by default. The page module adds `checkIdle()`, so a release that installed during a session takes over when it ends, and asks the browser to persist the copy. The headset test steps now serve `dist/` over plain HTTP, because `vite preview` with the IWSDK plugin uses a self-signed certificate that Quest Browser rejects for service workers.",
|
|
517
|
+
"packages": [
|
|
518
|
+
"@iwsdk/core"
|
|
519
|
+
]
|
|
520
|
+
},
|
|
521
|
+
{
|
|
522
|
+
"version": "1.2.0-rc.1",
|
|
523
|
+
"kind": "patch",
|
|
524
|
+
"text": "Generated projects gain an `iwsdk-offline` skill that makes an app run with no connection after one online visit. It ships the build script, the service worker template, and the page module as files the agent copies rather than retypes. The build script hashes every file in `dist/` and writes `sw.js`, the service worker keeps one hash-checked copy of the release and answers from it, and the page moves to a new release only when no XR session is running, or at the next load. Each file is downloaded once, an update downloads only the files whose hash changed, and the controller models and three.js decoders IWSDK fetches from CDNs are kept as well. The hosting and PWA packaging skills point to it for apps that must launch offline from the Horizon Store, and the PWA troubleshooting reference covers an installed app that shows an error page offline or an old release after a redeploy.",
|
|
525
|
+
"packages": [
|
|
526
|
+
"@iwsdk/core"
|
|
527
|
+
]
|
|
528
|
+
},
|
|
529
|
+
{
|
|
530
|
+
"version": "1.2.0-rc.1",
|
|
531
|
+
"kind": "patch",
|
|
532
|
+
"text": "Kinematic physics bodies now follow their Object3D, so the documented moving-platform pattern works. Before, moving a kinematic body's Object3D did nothing: the engine pose was written back every frame and the body snapped back. Now a changed Object3D pose is swept across the next physics substeps, so the body pushes dynamic bodies and carries anything resting on it. When the Object3D stops, the body is settled on its last pose instead of drifting on. Engine poses are no longer written back to kinematic bodies. `PhysicsManipulation` on a kinematic body is ignored with a one-time warning; move its Object3D instead. `setBodyTransform` still teleports a kinematic body without sweeping it.",
|
|
533
|
+
"packages": [
|
|
534
|
+
"@iwsdk/core"
|
|
535
|
+
]
|
|
536
|
+
},
|
|
537
|
+
{
|
|
538
|
+
"version": "1.2.0-rc.1",
|
|
539
|
+
"kind": "patch",
|
|
540
|
+
"text": "A model whose meshes have different vertex attributes (for example one mesh with vertex colours and one without, common in glTF) now gets a physics collider. Before, building its merged collider failed and `PhysicsSystem` threw on every frame. Merged colliders now use positions only, building one no longer changes the model's `matrixWorld`, and an entity whose collider can't be built logs one error and stays without a body instead of stopping the physics system.",
|
|
541
|
+
"packages": [
|
|
542
|
+
"@iwsdk/core"
|
|
543
|
+
]
|
|
544
|
+
},
|
|
545
|
+
{
|
|
546
|
+
"version": "1.2.0-rc.1",
|
|
547
|
+
"kind": "patch",
|
|
548
|
+
"text": "Physics colliders now follow an object's world scale. `Auto` shapes and mesh-derived `ConvexHull`/`TriMesh` shapes always use it: a box mesh scaled 2× used to get a 1 m collider and sink halfway into the floor. Spheres take the largest axis, and cylinders and capsules the larger horizontal axis for their radius. Mesh hulls also read interleaved position attributes correctly. Shapes with explicit `dimensions` keep their authored size by default, because those were often sized by hand to match a scaled visual. A scaled object with explicit dimensions logs a one-time warning, and the new `features.physics.applyScale: true` option applies scale to them too. That will become the default in a future release.",
|
|
549
|
+
"packages": [
|
|
550
|
+
"@iwsdk/core"
|
|
551
|
+
]
|
|
552
|
+
},
|
|
553
|
+
{
|
|
554
|
+
"version": "1.2.0-rc.1",
|
|
555
|
+
"kind": "patch",
|
|
556
|
+
"text": "Physics bodies under a transformed parent, such as a moved level root or another entity, now simulate in the right place. `PhysicsSystem` used to hand an entity's parent-relative pose to Havok as if it were a world pose, so a child of a parent 5 m up came to rest 5 m above the floor. Bodies are now created, driven, grabbed and rendered in world space and converted through the parent's transform. `setBodyTransform` accepts `{ space: 'world' }`; the default stays parent-relative (`'local'`).",
|
|
557
|
+
"packages": [
|
|
558
|
+
"@iwsdk/core"
|
|
559
|
+
]
|
|
560
|
+
},
|
|
561
|
+
{
|
|
562
|
+
"version": "1.2.0-rc.1",
|
|
563
|
+
"kind": "patch",
|
|
564
|
+
"text": "Emulated hand presses (`xr run-sequence` `press` steps) click small UIKit buttons again, and land on turned targets. The target resolver measured UIKit panels with component matrices UIKit had not computed yet, so a panel such as the starter's welcome panel was listed as a box reaching the XR origin (about 1.9 × 3.3 × 5.2 m). IWER routed every reach over that box, the fingertip came down onto the button from above, and pointerdown and pointerup landed on different elements, so no click fired even though the press reported contact. A panel's box also leaves out UIKit content that is hidden or scrolled out of view, and an element partly scrolled out of view is pressed on the part that shows; with less than 1 cm of it in view, such as a row that only touches the edge of its list, it counts as scrolled out of view and is neither listed nor pressed. A step that names such an element, or hidden content, by its UUID gets no target either, instead of the middle of where the element is laid out. Faces of turned objects come from the tighter of the object's own box and its axis-aligned box, and always lie on the axis-aligned box: on a row of keys turned 25°, the face of the axis-aligned box lay in front of the neighbouring key, which got the press. `place` sets a held object straight down onto the middle of a tilted top face instead of above it. A button on a UIKit panel that is itself turned (25° in testing) still misses, because IWER routes the reach over the button's own panel; that needs an IWER change. The `iwsdk-ui` skill and the `iwsdk-dev` skill's iteration reference now have agents confirm a press by the state it changes (`ui inspect` or app state): a `contactMs` of 800 or less means the fingertip touched something, not that the control clicked. They also have agents walk to a control out of reach (`body.stepTo`) as a step of its own before pressing it: a press that walks the body holds the touch past the 800 ms click window.",
|
|
565
|
+
"packages": [
|
|
566
|
+
"@iwsdk/core"
|
|
567
|
+
]
|
|
568
|
+
},
|
|
569
|
+
{
|
|
570
|
+
"version": "1.2.0-rc.1",
|
|
571
|
+
"kind": "patch",
|
|
572
|
+
"text": "`iwsdk browser profile` draws three warm-up frames before it starts sampling an app that renders on demand (headless sessions). The first profile of such a session used to include one-time first-draw costs (shader programs, texture uploads) and reported a frame-time p95 far above the app's real cost. The warm-up waits at most 5 seconds, within the command's time budget. If the frames are not drawn in time, for example because an uncaught error stopped the app's render loop, the profile reports a `render-warmup-timeout` interruption. A profile also reports `render-loop-stopped` when the app drew nothing for 30 or more animation frames in a row while the profile held rendering, because its render loop stopped (before or during the profile) or stalled; such profiles used to look like a healthy 60 fps. It reports `render-warmup-skipped-budget` (less than a second of the command's time left) or `render-mode-unavailable` when it has to sample without warm-up frames. Long tasks and event timings now count only work that starts during the profile. The `iwsdk-dev` skill's headless-rendering reference covers the warm-up and these interruptions.",
|
|
573
|
+
"packages": [
|
|
574
|
+
"@iwsdk/core",
|
|
575
|
+
"@iwsdk/vite-plugin-dev"
|
|
576
|
+
]
|
|
577
|
+
},
|
|
462
578
|
{
|
|
463
579
|
"version": "1.2.0-rc.0",
|
|
464
580
|
"kind": "minor",
|
|
@@ -1061,6 +1177,14 @@
|
|
|
1061
1177
|
"@iwsdk/vite-plugin-dev"
|
|
1062
1178
|
]
|
|
1063
1179
|
},
|
|
1180
|
+
{
|
|
1181
|
+
"version": "1.2.0-rc.1",
|
|
1182
|
+
"kind": "patch",
|
|
1183
|
+
"text": "Adding IWSDK to an existing project now works when its `package.json` doesn't declare `\"type\": \"module\"`, which includes projects made with `npm init -y`: the new Vite config is written as `vite.config.mjs`/`.mts`. A Vite config that Vite loads as CommonJS is left alone, with renaming it to `.mjs`/`.mts` listed as a step, also when it already imports the IWSDK plugin (as the configs that 1.2.0-rc.0 wrote do). With several Vite configs, Create edits none and names the one Vite loads. Adoption also leaves locomotion off unless you ask for it (`--locomotion`, or Yes in the customize prompt, which now starts at No), because the scene it writes has no floor and the player would fall; the report says so, and lists the floor when an existing `iwsdk.config.json` turns locomotion on over a scene without `LocomotionEnvironment`. Requests for the same release no longer print \"newer than this release\", and a dist-tag such as `latest` is reported as one.",
|
|
1184
|
+
"packages": [
|
|
1185
|
+
"@iwsdk/create"
|
|
1186
|
+
]
|
|
1187
|
+
},
|
|
1064
1188
|
{
|
|
1065
1189
|
"version": "1.2.0-rc.0",
|
|
1066
1190
|
"kind": "patch",
|
|
@@ -1210,6 +1334,14 @@
|
|
|
1210
1334
|
"@iwsdk/reference-assets"
|
|
1211
1335
|
]
|
|
1212
1336
|
},
|
|
1337
|
+
{
|
|
1338
|
+
"version": "1.2.0-rc.1",
|
|
1339
|
+
"kind": "patch",
|
|
1340
|
+
"text": "The emulator dependencies (`iwer`, `@iwer/sem`, `@iwer/devui`) move to ^2.9.0, the IWER release that ships alongside `@iwer/native`. The browser emulator behaves as on 2.8.",
|
|
1341
|
+
"packages": [
|
|
1342
|
+
"@iwsdk/vite-plugin-dev"
|
|
1343
|
+
]
|
|
1344
|
+
},
|
|
1213
1345
|
{
|
|
1214
1346
|
"version": "1.2.0-rc.0",
|
|
1215
1347
|
"kind": "patch",
|
package/dist/version.d.ts
CHANGED