[bug]: npx shadcn init hangs while creating nextjs project

[matt-seifert]

Describe the bug

When I run the command "npx shadcn init" or "npx shadcn@latest init", I'm prompted with the first two questions (Would you like to start a new nextjs project/What is your project's name). Once I select the name, the CLI says "Creating a new Next.js project. This may take a few minutes.". But it just sits there indefinitely and never creates anything, forcing me to eventually terminate the process. This was working fine 2 days ago, but I've been getting this bug since yesterday afternoon. Have verified this bug is operating similarly on 2 of my machines, and I had my friend verify on his machine as well.

Affected component/components

All

How to reproduce

Run "npx shadcn init" command and try to start a new nextjs project.

Codesandbox/StackBlitz link

No response

Logs

No response

System Info

Windows 11 Version	10.0.26100 Build 26100

Before submitting

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

[Wangbaoqi]

me too

[shokks]

Me too.

Is this caused by the NextJS15 released last night, where it supports React@19 RC?

clean install of create-next-app@latest gives you a fresh copy where, if you run, npx shadcn@latest init throws error with the fact that nextjs15 uses, [email protected] and @radix-ui/react-icons & @radix-ui/[email protected] use react@"^16.x || ^17.x || ^18.x"

Dependency errors, maybe?

[matt-seifert]

Me too.

Is this caused by the NextJS15 released last night, where it supports React@19 RC?

clean install of create-next-app@latest gives you a fresh copy where, if you run, npx shadcn@latest init throws error with the fact that nextjs15 uses, [email protected] and @radix-ui/react-icons & @radix-ui/[email protected] use react@"^16.x || ^17.x || ^18.x"

Dependency errors, maybe?

Great sleuthing there! Sounds like a strong possibility.

[JeffinJ]

Same here, a new app with NextJS 15, and when installing shadcn/ui

[codmanuel26]

I'm having the same problem it was working yesterday in the morning

[aajuu19]

Same problem for me. Peer dependency issue for sure because of the different react version.

If you need it asap, you can use the --legacy-peer-deps flag:
npx --legacy-peer-deps shadcn@latest init

This works for now and we should then later be able to update it to the latest version 😄

[matt-seifert]

Same problem for me. Peer dependency issue for sure because of the different react version.

If you need it asap, you can use the --legacy-peer-deps flag: npx --legacy-peer-deps shadcn@latest init

This works for now and we should then later be able to update it to the latest version 😄

Thanks for the response and suggestion. Unfortunately this command still causes it to hang while creating the Next.js project. I was, however, able to do "npx [email protected]", followed by "npx shadcn init", and it seems to scaffold everything correctly. I believe Next.js version before the breaking change is 14.2, so this puts the project one version behind current. I think once things are fixed, the update to Next.js 15 should be simple. Still would rather just have the simple "npx shadcn init" worrking correctly!

[codmanuel26]

how would I do this to work with V0's block system

[shadcn]

Was an issue with React 19 peer deps. I temporarily pinned the deps. Should be okay now. Let me know if not.

[shadcn]

I'm working on a fix. Let's use #5557 to track since they are related.