FileViewerSheet's code-line highlight referenced --paperclip-code-highlight-bg / --paperclip-code-highlight-border without either var ever being defined, so rendering always came from the var() fallbacks. Define both in the extracted-tokens :root block at exactly the former fallback values (rgba(250,204,21,0.12) / rgb(234,179,8)) and drop the now-redundant fallbacks from the Batch 4 --code-highlight-*-resolved wrappers. Call sites in FileViewerSheet.tsx unchanged. Nothing anywhere sets these vars at runtime (verified via rg), so pixels are identical. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| storybook | ||
| README.md | ||
| components.json | ||
| index.html | ||
| package.json | ||
| tsconfig.json | ||
| vite.config.ts | ||
| vitest.config.ts | ||
| vitest.setup.ts | ||
README.md
@paperclipai/ui
Published static assets for the Paperclip board UI.
What gets published
The npm package contains the production build under dist/. It does not ship the UI source tree or workspace-only dependencies.
Storybook
Storybook config, stories, and fixtures live under ui/storybook/.
pnpm --filter @paperclipai/ui storybook
pnpm --filter @paperclipai/ui build-storybook
Typical use
Install the package, then serve or copy the built files from node_modules/@paperclipai/ui/dist.