[bug]:

[shorty-huddybuddy]

Describe the bug

npx shadcn@latest init -d

✔ Preflight checks.
✔ Verifying framework. Found Next.js.
✔ Validating Tailwind CSS config. Found v4.
✔ Validating import alias.

Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

Validation failed:

• tailwind: Required

while installing this issue persists , what to do ?

Affected component/components

tailwind

How to reproduce

npx shadcn@latest init -d

✔ Preflight checks.
✔ Verifying framework. Found Next.js.
✔ Validating Tailwind CSS config. Found v4.
✔ Validating import alias.

Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

Validation failed:

• tailwind: Required

Codesandbox/StackBlitz link

No response

Logs

System Info

Microsoft

Before submitting

• I've made research efforts and searched the documentation
• I've searched for existing issues

[ariel-nathan]

Seeing the same issue using Bun and Vite.
Tried initializing in a brand new empty project using bun create vite@latest --template react-ts.

Followed the docs:

• Added @import "tailwindcss"; to the top of the src/index.css file
• Updated both tsconfig.json and tsconfig.app.json with the path aliases
• Updated the vite config with the tailwindcss vite plugin and the path alias

I also verified that TailwindCSS is actually working by adding some styles.

CLI output:

> bunx --bun shadcn@latest init -d
✔ Preflight checks.
✔ Verifying framework. Found Vite.
✔ Validating Tailwind CSS config. Found v4.
✔ Validating import alias.

Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

Validation failed:
- tailwind: Required

[ariel-nathan]

If I exclude the -d flag from bunx --bun shadcn@latest init, and manually choose a color, it initializes successfully.

[body20002]

I have the same issue running pnpm shadcn@latest init -d fails while pnpm shadcn@latest init initializes successfully.

[marcospassos]

Same error here