npm: scope cultnet-ts, cultmesh-ts, cultmesh-browser under @gamecult #28

Merged
libby merged 1 commit from libby/scope-npm-packages into main 2026-11-07 16:25:15 +00:00
Member

Renames the unscoped npm packages cultnet-ts, cultmesh-ts, cultmesh-browser to @gamecult/... (cultcache-ts was already scoped), so the unscoped names cannot be claimed by someone else. Nothing is published.

Changed: package.json names and intra-repo dependencies, package-lock.json (regenerated with --package-lock-only), import specifiers in src/tests/samples/docs-start (incl. the first-call docs test, which compares the README snippet to the test), scripts/run-typescript-workspaces.mjs workspace list, scripts/verify-eve-browser-network.mjs module map, package READMEs and the live docs, plus a Breaking note in each package's CHANGELOG.
Unchanged: directory names, --workspace packages/... paths in CI, release tag prefixes, historical cut docs and old CHANGELOG entries, .voidbot snapshots.

Verified locally

  • npm run test:pack:ts package-closure smoke: passed (4 scoped tarballs pack and install, entries resolve).
  • cultnet-ts: first-call, idunn-runtime-authority and content tests: 72 run, 71 pass; the failure is the esbuild-browser case (reads the workspace-parent package.json, env-specific; same case the backlog lists as the suite hang).
  • cultmesh-browser npm test: 51 run, 50 pass; same esbuild-browser case.
  • cultmesh-ts: 161 pass, 0 fail (219 run).
  • check-typescript-tests-wired: pass.

Already red on main, identical here (not touched)

  • npm run build:ts fails in cultmesh-ts with 6 TS2345 errors (error messages lacking routingHint/code/details since #20); same 6 on main at 655cb2c9. I ran the cultmesh tests on the emitted dist and packed with scripts ignored.
  • scripts/test-declared-dependency-ranges.mjs: cultmesh-ts's @gamecult/cultcache-ts ^0.14.0 admits a tag lacking six exports; untouched range line.

🤖 Generated with Claude Code

Renames the unscoped npm packages `cultnet-ts`, `cultmesh-ts`, `cultmesh-browser` to `@gamecult/...` (cultcache-ts was already scoped), so the unscoped names cannot be claimed by someone else. Nothing is published. Changed: package.json names and intra-repo dependencies, `package-lock.json` (regenerated with `--package-lock-only`), import specifiers in src/tests/samples/docs-start (incl. the first-call docs test, which compares the README snippet to the test), `scripts/run-typescript-workspaces.mjs` workspace list, `scripts/verify-eve-browser-network.mjs` module map, package READMEs and the live docs, plus a Breaking note in each package's CHANGELOG. Unchanged: directory names, `--workspace packages/...` paths in CI, release tag prefixes, historical cut docs and old CHANGELOG entries, `.voidbot` snapshots. ## Verified locally - `npm run test:pack:ts` package-closure smoke: passed (4 scoped tarballs pack and install, entries resolve). - cultnet-ts: first-call, idunn-runtime-authority and content tests: 72 run, 71 pass; the failure is the esbuild-browser case (reads the workspace-parent `package.json`, env-specific; same case the backlog lists as the suite hang). - cultmesh-browser `npm test`: 51 run, 50 pass; same esbuild-browser case. - cultmesh-ts: 161 pass, 0 fail (219 run). - `check-typescript-tests-wired`: pass. ## Already red on main, identical here (not touched) - `npm run build:ts` fails in cultmesh-ts with 6 TS2345 errors (error messages lacking `routingHint/code/details` since #20); same 6 on main at 655cb2c9. I ran the cultmesh tests on the emitted dist and packed with scripts ignored. - `scripts/test-declared-dependency-ranges.mjs`: cultmesh-ts's `@gamecult/cultcache-ts ^0.14.0` admits a tag lacking six exports; untouched range line. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
npm: scope cultnet-ts, cultmesh-ts and cultmesh-browser under @gamecult
Some checks failed
CultMesh QUIC native / Build win32-x64 (pull_request) Has been skipped
CultMesh QUIC native / Build linux-x64 (pull_request) Has been skipped
CultMesh QUIC native / Release native binaries (pull_request) Has been skipped
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Failing after 5m49s
CultMesh QUIC native / Verify committed binaries match SHA256SUMS (pull_request) Successful in 36s
286a9af389
Unscoped npm names are unclaimed and open to dependency confusion; cultcache-ts was
already @gamecult/cultcache-ts. package.json names, intra-repo dependencies, package-lock,
import specifiers (src, tests, samples, docs/start, first-call docs test), the workspace
list in run-typescript-workspaces, the verify-eve module map and package READMEs now use
the scoped names. Directory names, workspace paths in CI and release tag prefixes are
unchanged. Historical cut docs and past CHANGELOG entries keep the old names.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
libby merged commit 8477d8dc74 into main 2026-11-07 16:25:15 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
GameCult/CultLib!28
No description provided.