Skip to content

fix(examples): correct Tailwind @source paths in chat and harness-chat - #313

Open
adhamali450 wants to merge 1 commit into
vercel-labs:mainfrom
adhamali450:fix/example-tailwind-source-paths
Open

fix(examples): correct Tailwind @source paths in chat and harness-chat#313
adhamali450 wants to merge 1 commit into
vercel-labs:mainfrom
adhamali450:fix/example-tailwind-source-paths

Conversation

@adhamali450

Copy link
Copy Markdown

Fixes #312

What

  • examples/chat/app/globals.css: add @source "../../../packages/shadcn/src/**/*.tsx", matching no-ai, next-website-builder, and mcp, so catalog-only utilities are generated
  • chat and harness-chat: fix the streamdown @source path from ../../../node_modules/... (repo root, empty under pnpm) to ../node_modules/..., matching apps/web

Why

Tailwind v4 skips node_modules and gitignored dist when scanning sources, so classes that only exist in the built @json-render/shadcn package never reach the generated CSS. A Grid with columns: 4 renders correct DOM with dead class names.

Testing

Prompted the chat example for a 4x4 card grid and a justify="around" stack. grid-cols-1..6 and justify-around now appear in the served CSS and layouts render correctly.

The chat example never scanned the @json-render/shadcn package, so
classes that only occur inside it (grid-cols-4, justify-around, etc.)
were missing from the generated CSS. Other examples already scan
packages/shadcn/src. This aligns chat with that convention.

Also fixes the streamdown @source path in chat and harness-chat.
"../../../node_modules" points at the repo root, which is empty under
pnpm. Dependencies are linked into each example's own node_modules,
as apps/web already assumes.
@vercel

vercel Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

@adhamali450 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Chat example: catalog-only Tailwind classes (e.g. grid-cols-4) have no CSS

1 participant