@helix3/helix-cli 0.1.13-helix3.102 → 0.1.13-helix3.103
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 +21 -0
- package/package.json +3 -2
package/README.md
CHANGED
|
@@ -101,6 +101,27 @@ connection resumes the same Build rather than minting a second one.
|
|
|
101
101
|
Only **shared-runtime** worlds publish this way. A World Build may not contain creator
|
|
102
102
|
executables, so `native-game` builds are a separate distribution path.
|
|
103
103
|
|
|
104
|
+
## Working in a git worktree? Run this first
|
|
105
|
+
|
|
106
|
+
```
|
|
107
|
+
npm run check:dev-links
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
`package.json` links its sibling HELIX packages by relative path
|
|
111
|
+
(`file:../helix-manifest`, `file:../helix-web-sdk`). That is right in the canonical
|
|
112
|
+
layout, where the siblings sit beside this clone — but in a **git worktree** `../` is
|
|
113
|
+
the worktree parent, so the links resolve to whatever happens to be there: a checkout
|
|
114
|
+
parked on an older branch, or nothing at all.
|
|
115
|
+
|
|
116
|
+
The symptom is not "broken dev link". It is **a branch that looks broken**: `tsc`
|
|
117
|
+
reporting `has no exported member …` in files your change never touched, and whole
|
|
118
|
+
suites failing at import (`could not find the dev shell in @hypersoniclabs/helix-sdk`).
|
|
119
|
+
People have concluded a PR was broken on the strength of exactly this.
|
|
120
|
+
|
|
121
|
+
`check:dev-links` names which link is wrong, which imported symbols the linked sibling
|
|
122
|
+
does not export, and how to fix it without repointing a shared directory other
|
|
123
|
+
worktrees resolve through.
|
|
124
|
+
|
|
104
125
|
## Publish flow
|
|
105
126
|
|
|
106
127
|
`helix publish` maps directly onto the backend's Instant World API:
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@helix3/helix-cli",
|
|
3
|
-
"version": "0.1.13-helix3.
|
|
3
|
+
"version": "0.1.13-helix3.103",
|
|
4
4
|
"description": "helix — the HELIX creator CLI: scaffold, validate, and publish Instant Worlds",
|
|
5
5
|
"main": "dist/lib.js",
|
|
6
6
|
"types": "dist/lib.d.ts",
|
|
@@ -34,7 +34,8 @@
|
|
|
34
34
|
"build": "tsc -p tsconfig.build.json",
|
|
35
35
|
"lint": "eslint \"src/**/*.ts\"",
|
|
36
36
|
"test": "node --experimental-vm-modules node_modules/jest/bin/jest.js",
|
|
37
|
-
"qa:vault-lifecycle": "npm run build && node scripts/run-vault-lifecycle-qa.mjs"
|
|
37
|
+
"qa:vault-lifecycle": "npm run build && node scripts/run-vault-lifecycle-qa.mjs",
|
|
38
|
+
"check:dev-links": "node scripts/check-dev-links.mjs"
|
|
38
39
|
},
|
|
39
40
|
"dependencies": {
|
|
40
41
|
"@gltf-transform/core": "^4.4.0",
|