CLI registry fetch fails (Vercel + Netlify) -> init/add cannot work
## Problem
The `shadcn-solid` CLI cannot fetch the registry, so both `init` and `add` flows are blocked.
I am seeing:
- `[framework] Failed to fetch registry` (during `init`)
- `[component] Failed to fetch registry` (during `add`)
## Environment
- OS: Linux
- Package manager: `bun` / `bunx`
- `bun --version`: `1.3.2`
- CLI: `shadcn-solid@latest` (also observed with cached `shadcn-solid@0.7.7`)
## Repro
### 1) `init`
```bash
cd Code/Auth/Frontend
bunx shadcn-solid@latest init
```
Output:
```text
[framework] Failed to fetch registry
```
### 2) `add` (after valid `components.json`)
```bash
cd Code/Auth/Frontend
bunx shadcn-solid@latest add separator
```
Output:
```text
[component] Failed to fetch registry
```
## What I checked
The CLI appears to fetch from the hosted registry endpoint (default registry URL).
These endpoints currently return `404`:
- `https://shadcn-solid.vercel.app/registry/index.json`
- `https://shadcn-solid.netlify.app/registry/index.json`
I also tried overriding the CLI registry URL:
```bash
REGISTRY_URL=https://shadcn-solid.netlify.app bunx shadcn-solid@latest add separator
```
but it still fails with:
```text
[component] Failed to fetch registry
```
## Expected behavior
- `init` should create `components.json`
- `add separator` should download registry metadata/component source and generate files
## Actual behavior
Registry fetch fails, so CLI workflow is unusable.
## Notes
As a workaround, I can manually copy components from the local repo registry sources (`apps/docs/src/registry/...`), but the CLI install flow is currently blocked.
If the registry host changed, maybe the CLI default URL (or docs) needs updating.
关闭于 2026-02-25 1 条评论