[bug]: shadcn CLI stuck at "Checking registry..." (Windows + Bun / npx)

[baohg1108]

Describe the bug

When running the shadcn CLI to add components, the process gets stuck at:

Checking registry.

and does not proceed further ~~

bunx shadcn@latest add form
or:
npx shadcn@latest add form
=> The CLI stops at "Checking registry..."

Affected component/components

form, CLI

How to reproduce

1. Open terminal on Windows
2. Run: bunx shadcn@latest add form
3. Or run: npx shadcn@latest add form
4. Observe that the CLI stops at "Checking registry..."
5. It does not proceed or show any error

Codesandbox/StackBlitz link

No response

Logs

$ bunx shadcn@latest add form
✔ Checking registry.

$ npx shadcn@latest add form
✔ Checking registry.

System Info

OS: Windows 10 
Node: (22.20.0)
Bun: (1.3.11)
Package manager: bun / npm
Framework: Next.js

Before submitting

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

[swastik7805]

hey @baohg1108 ,I tried reproducing the error but i did not encounter any such issue.

Could you be more descriptive in your bug or issue.

[CarlosGamez-Nova]

I get an error:

> bunx --bun shadcn-vue@latest add sidebar

Something went wrong. Please check the error below for more details.                                                                           11:00:04 PM
If the problem persists, please open an issue on GitHub.                                                                                       11:00:04 PM
                                                                                                                                               11:00:04 PM
Message:                                                                                                                                       11:00:04 PM
The item at https://shadcn-vue.com/r/styles/new-york-v4/icon-placeholder.json was not found. It may not exist at the registry.                 11:00:04 PM
                                                                                                                                               11:00:04 PM
Suggestion:
Check if the item name is correct and the registry URL is accessible.