CLI gets stuck when adding `--add-ons shadcn`

[owen-vey]

Which project does this relate to?

Create Tanstack App

Describe the bug

When running the following command:
npx create-tsrouter-app@latest --add-ons shadcn

the CLI seems to hang infinitely on Setting up Shadcn... as shown below:

Your Example Website or App

N/A

Steps to Reproduce the Bug or Issue

1. Run npx create-tsrouter-app@latest --add-ons shadcn from the Terminal
2. Observe that the CLI gets stuck on the "Setting up Shadcn..." step

Expected behavior

As a user, I expected the CLI to correctly set up Shadcn but I am seeing it stuck on "Setting up Shadcn..." and no warning or error is printed.

Screenshots or Videos

See above

Platform

• OS: macOS
• Node Version: v22.13.1

[anthony2261]

Same here +1

[jherr]

Shadcn is the only add-on that runs a command. So a couple of questions:

1. Can you run npx shadcn@canary init -d -s on your machine an in a project?
2. Does it get stuck if you just run npx create-tsrouter-app@latest --add-ons and you follow the prompts to make the same choice

[owen-vey]

1. npx shadcn@canary init -d -s ran fine on my machine

2. Yes, it still gets stuck when running npx create-tsrouter-app@latest --add-ons and selecting Shadcn from the prompt

[owen-vey]

I went and tested running npx create-tsrouter-app@latest and selected file-router. I then went and ran npx shadcn@canary init -d -s after the project was created and saw the following errors:

I then went and created a new project with npx create-tsrouter-app@latest --tailwind and was left with just the last error:

Just a thought, but maybe you need to add

resolve: {
  alias: {
    "@": path.resolve(__dirname, "./src"),
  },
},

to vite.config.ts before running the shadcn CLI https://ui.shadcn.com/docs/installation/vite#update-viteconfigts

(as well as ensure Tailwind is installed and setup before prior)

[jherr]

We definitely do add:

resolve: {
  alias: {
    "@": path.resolve(__dirname, "./src"),
  },
},

To the vite.config.ts if shadcn is enabled. I'm kinda considering just adding it all the time as its super handy.

I haven't see the React 19 warning. Interesting. If you add the --force does it work without complaint?

Worst case scenario I can just remove the npx command and manually put whatever changes it makes into the add-on itself.

[owen-vey]

Even with --force I still see the warning and have to choose a selection

It looks like it is just an issue with npm. More info here https://ui.shadcn.com/docs/react-19#tldr

[jherr]

I think I see what's happening. This is creating a new Next.js app. Yeah, to repro we really need to run that npx command within the half-built ts-router app.

I think the best thing to do is for me to just apply the patches that it makes manually in the add-on.

[owen-vey]

Weirdly enough, when I pull down and build the repo locally and run pnpm start --add-ons and select Shadcn it works fine 🤔

[jherr]

Deep sigh.

Well, I still thin the best thing to do is not run the command and to apply the patches myself. That's what we do for solid-ui since it doesn't even have a silent option.

[jherr]

Ok, should definitely be fixed now since we are no longer running the init command. Be sure to use @latest.

[owen-vey]

@jherr Yep that fixed it. I now see the same issue happening when the CLI is trying to add shadcn components once start is included in the add-ons:

[jherr]

Ok, different issue, same source-ish, which is running commands. My only thought is that somehow the CWD is set wrong. Are you running on Windows or something? Is there some way the CWD could be set incorrectly?

[owen-vey]

I'm on Mac, pretty standard shell setup. Let me try on another Macbook and see if I have the same issue.