mirror of
https://github.com/backnotprop/plannotator.git
synced 2026-09-14 14:17:26 +08:00
Michael Ramos
b5acac64d6
@plannotator/ui 0.38.0 does not install into a consumer: config/settings.ts imports @plannotator/core/token-hover (#1462), but that PR added the export to core without bumping it, so 0.38.0 pins core 0.25.1, which never published the subpath. Every host reaches it through configure -> config -> settings, so typecheck and build fail on the first import. core 0.25.2 publishes ./token-hover plus the other changes core accumulated since 0.25.1 (the rotated guide-viewer-manifest pin, the config-types hover fields). ui 0.38.1 is 0.38.0 pinning core 0.25.2, and aligns @codemirror/state to ^6.7.2 beside @codemirror/view ^6.43.10 so a consumer cannot resolve two state copies. The package smoke passed on 0.38.0 because its external consumer installs core from the LOCAL tarball (pnpm override), so an export that exists in source but not on the registry is invisible to it, and its consumer entry never imported the configure/config path. It now (1) collects every @plannotator/core/<subpath> the UI source imports and asserts each is an export of the core source manifest, (2) when the pinned core version is already on the registry, asserts each is exported by THAT published core and that the core source exports match it exactly (otherwise: bump core and publish it first), printing a publish-core-first reminder when the pinned version is not published yet, and (3) compiles @plannotator/ui/configure and @plannotator/ui/config in the external consumer's vite build and tsc. With the pins set back to 0.38.0's, the smoke now fails naming token-hover. HANDOFF and README: current pair 0.38.1 on 0.25.2; do not consume 0.38.0.