-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug]: init and install component failed #5565
Comments
I also have this problem and am looking forward to a solution. The new cli cannot be downloaded. |
Same problem on create-next-app@latest. Tried deleting node_modules and shadcn dependencies from package.json still having errors while initializing shadcn. edit: adding npm install |
i am also facing this issue i am using linux ubuntu |
ya me to having this error in next15 we can hope shadcn team fix it really soon |
Prefer manual install wait for devs to upgrade to react 19 |
I'm encountering the same problem with Next 14, receiving the message:
Is there any fix or workaround available? |
same problem here 😢 |
No, I haven't upgraded my NextJS to 15 and still have this issue. |
I haven't upgraded my NextJS to 15 and still have this issue |
I'm working on a fix. Let's use #5557 to track since they are related. |
But I am not using nextjs15, I am still using next 14, Since I am in China, I use the domestic npm mirror source. Is it because of this reason? |
Describe the bug
$ npx shadcn@latest init
✔ Preflight checks.
✔ Verifying framework. Found Next.js.
✔ Validating Tailwind CSS.
✔ Validating import alias.
Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.
request to https://ui.shadcn.com/r/styles/index.json failed, reason: connect ETIMEDOUT 76.76.21.98:443
Affected component/components
install
How to reproduce
My address is not in the United States and I downloaded it through a VPN, but it still doesn’t work.
Codesandbox/StackBlitz link
1
Logs
No response
System Info
Before submitting
The text was updated successfully, but these errors were encountered: