Matthew L McPeak
23cb57420d
Two independent fixes: 1. Alert titles used text-<severity> directly on a bg-<severity>/15 tinted background. For danger (a very dark base hue) this reads as near-invisible text-on-tinted-background. The original PrimeVue-era Message design kept body/title text neutral and only accented the icon/left-border with the severity color -- restore that: alert text stays text-foreground, severity shows via a border-l-4 accent stripe instead of tinted text. 2. Root-caused why none of the last several fixes were showing up without a full `bun run build`: @nychthemeron/library's package.json exports its "." entry as ./dist/index.js unconditionally, and every story imports from the bare package specifier. So Storybook's dev server was always resolving to whatever the dist bundle looked like at last build time, never live source -- editing packages/library/src and restarting `bun run dev` (even with caches cleared) never picked up changes. Vite auto-injects a "development" resolution condition during `vite dev`/serve (and "production" during build), which is the standard fix for exactly this monorepo dev-vs-published split: added a "development" condition to the "." export pointing at src/index.ts, matching the pattern the "./components" sub-export already used. Also added the matching "@" alias to packages/playground/vite.config.ts, since resolving straight to library source pulls in its "@/lib/utils"-style internal imports, which playground's own Vite instance didn't previously know how to resolve. Verified both paths: dev server now reflects source edits without a library rebuild, and `bun run build` still produces a correct dist bundle with the same fix baked in. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| .storybook | ||
| public | ||
| stories | ||
| Dockerfile | ||
| package.json | ||
| tsconfig.json | ||
| vite.config.ts | ||