You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(appkit): keep node: cache-path resolver out of the client-safe shared barrel
CI surfaced two failures from routing the cache-path resolvers through the
shared root barrel:
1. Docs Build (+ PR Template): the root barrel `shared/src/index.ts` is
client-safe (docs webpack aliases shared->src and pulls it via appkit-ui),
but cache-paths imports `node:path`, so the docs client bundle died with
UnhandledSchemeError. Move the resolvers off the root barrel onto a
Node-only subpath and import them there from appkit's cache/serving/
choice-sink modules. tsdown owns shared's generated `exports` (devExports),
so the subpath is added as a tsdown entry and keyed by its src-relative
path: `shared/cli/commands/cache-paths`.
2. Unit Tests: the new bootstrap-vs-drift message assertions matched raw text,
but picocolors emits ANSI codes when CI is set, splitting the strings. Strip
ANSI (incl. the ESC byte) before matching. Also repoint the cache
serialization test's `vi.mock` to the new subpath specifier.
Verified with the gates CI runs: `CI=true pnpm test` (3725 pass), `pnpm
docs:build` (client compiles, no node: error), typecheck, build, check, knip.
xavier loop: iteration 6 -- CI fixes (docs node: leak + ANSI-brittle tests)
Co-authored-by: Isaac
Signed-off-by: Atila Fassina <atila@fassina.eu>
0 commit comments