mosaic gateway install was failing with ERR_PACKAGE_PATH_NOT_EXPORTED because the published @mosaic/[email protected] on the Gitea registry is the old tooling-configs package (tsconfig/eslint/prettier), not the runtime config loader that commit 04a80fb9 repurposed the package into. Version was never bumped, so consumers kept pulling the stale tarball.
Changes
@mosaic/config: 0.0.1 → 0.0.2 (triggers publish of runtime variant with . export)
@mosaic/gateway: 0.1.0 → 0.0.5 (republish with fixed dep; 0.1.0 was an unintended semver jump and has been deleted from the Gitea registry to restore the 0.0.x lineage)
@mosaic/mosaic: 0.0.18 → 0.0.19 (CLI ships with fixed transitive resolution)
Test plan
pnpm typecheck passes
pnpm lint passes
pnpm format:check passes
CI publish pipeline pushes new versions to Gitea registry
mosaic gateway install succeeds and gateway becomes healthy
## Summary
`mosaic gateway install` was failing with `ERR_PACKAGE_PATH_NOT_EXPORTED` because the published `@mosaic/[email protected]` on the Gitea registry is the old tooling-configs package (tsconfig/eslint/prettier), not the runtime config loader that commit 04a80fb9 repurposed the package into. Version was never bumped, so consumers kept pulling the stale tarball.
## Changes
- `@mosaic/config`: 0.0.1 → 0.0.2 (triggers publish of runtime variant with `.` export)
- `@mosaic/gateway`: 0.1.0 → 0.0.5 (republish with fixed dep; 0.1.0 was an unintended semver jump and has been deleted from the Gitea registry to restore the 0.0.x lineage)
- `@mosaic/mosaic`: 0.0.18 → 0.0.19 (CLI ships with fixed transitive resolution)
## Test plan
- [x] `pnpm typecheck` passes
- [x] `pnpm lint` passes
- [x] `pnpm format:check` passes
- [ ] CI publish pipeline pushes new versions to Gitea registry
- [ ] `mosaic gateway install` succeeds and gateway becomes healthy
The published @mosaic/[email protected] on the Gitea registry is the
stale tooling-configs package (tsconfig/eslint/prettier) with only
subpath exports. When the package was repurposed in 04a80fb9 as the
runtime config loader, its version was never bumped, so consumers
that pull from the registry still get the old tarball.
This caused `mosaic gateway install` to fail with
ERR_PACKAGE_PATH_NOT_EXPORTED when gateway imported loadConfig from
@mosaic/config at runtime.
- Bump @mosaic/config to 0.0.2 so CI publishes the runtime variant
- Bump @mosaic/gateway to 0.0.5 to republish with the fixed dep
(0.1.0 was an unintended semver jump; deleted from registry to
restore 0.0.x lineage)
- Bump @mosaic/mosaic to 0.0.19 so the CLI ships with the fixed
transitive dep resolution
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
mosaic gateway installwas failing withERR_PACKAGE_PATH_NOT_EXPORTEDbecause the published@mosaic/[email protected]on the Gitea registry is the old tooling-configs package (tsconfig/eslint/prettier), not the runtime config loader that commit04a80fb9repurposed the package into. Version was never bumped, so consumers kept pulling the stale tarball.Changes
@mosaic/config: 0.0.1 → 0.0.2 (triggers publish of runtime variant with.export)@mosaic/gateway: 0.1.0 → 0.0.5 (republish with fixed dep; 0.1.0 was an unintended semver jump and has been deleted from the Gitea registry to restore the 0.0.x lineage)@mosaic/mosaic: 0.0.18 → 0.0.19 (CLI ships with fixed transitive resolution)Test plan
pnpm typecheckpassespnpm lintpassespnpm format:checkpassesmosaic gateway installsucceeds and gateway becomes healthy