◐ Initializing project.. [CLI Error]: Failed to fetch base color from registry.

[Kaidstor]

Describe the bug

when starting initialize project it cant get the registry and https://next.shadcn-svelte.com/registry response with 404

same issue on adding
bun x shadcn-svelte@next add button

shadcn-svelte v1.0.0-next.6
│
▲ Incompatible dependency versions detected:
│
│ need tailwindcss@3.x.x >> found 4.0.12
│
│ Use at your own risk!
│
└ [CLI Error]: Failed to fetch components from registry.

Reproduction

commands:

bun x shadcn-svelte@next init
bun x shadcn-svelte@next add button

workspace (tauri 2, empty proj) with bun

components.json

{
	"$schema": "https://next.shadcn-svelte.com/schema.json",
	"style": "default",
	"tailwind": {
		"config": "tailwind.config.js",
		"css": "src/app.css",
		"baseColor": "stone"
	},
	"aliases": {
		"components": "$lib/components",
		"utils": "$lib/utils",
		"ui": "$lib/components/ui",
		"hooks": "$lib/hooks"
	},
	"typescript": true,
	"registry": "https://next.shadcn-svelte.com/registry"
}

Logs

System Info

System:
    OS: macOS 15.3.1
    CPU: (12) arm64 Apple M2 Max
    Memory: 279.22 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.13.1 - ~/.local/state/fnm_multishells/3943_1741340700466/bin/node
    npm: 10.9.2 - ~/.local/state/fnm_multishells/3943_1741340700466/bin/npm
    pnpm: 10.2.0 - /opt/homebrew/bin/pnpm
    bun: 1.2.1 - ~/.bun/bin/bun
  Browsers:
    Safari: 18.3
  npmPackages:
    @sveltejs/kit: ^2.9.0 => 2.18.0 
    bits-ui: ^1.3.6 => 1.3.6 
    svelte: ^5.0.0 => 5.22.2 
    tailwindcss: ^4.0.12 => 4.0.12

Severity

annoyance

[ieedan]

So next.shadcn-svelte.com/registry is just a basepath for a registry so it will always show a 404 since it isn't intended to exist.

Currently I am unable to reproduce this. Maybe your network is somehow blocking it?

[Kaidstor]

can i see trace or more detail info about error? to reproduce u more info? idk how to check endpoint that throw this error

[Kaidstor]

i try to proxy my query and it dont help me

[ieedan]

can i see trace or more detail info about error? to reproduce u more info? idk how to check endpoint that throw this error

Might be worth adding since we are getting more of these errors now but it doesn't currently exist.

Try this:

curl https://next.shadcn-svelte.com/registry/index.json

See if you still get the error

[Kaidstor]

curl https://next.shadcn-svelte.com/registry/index.json
[
{
"name": "accordion",
"type": "registry:ui",
"dependencies": [
"bits-ui"
],
"registryDependencies": [],
"files": [
{
"path": "ui/accordion/accordion-content.svelte",
"type": "registry:ui"
},
{
"path": "ui/accordion/accordion-item.svelte",
"type": "registry:ui"
},
{
"path": "ui/accordion/accordion-trigger.svelte",
"type": "registry:ui"
},
{
"path": "ui/accordion/index.ts",
"type": "registry:ui"
}
]
},
{
"name": "alert",
"type": "registry:ui",
"dependencies": [
"bits-ui"
],
"registryDependencies": [],
"files": [
{
"path": "ui/alert/alert-description.svelte",
"type": "registry:ui"
},
{
"path": "ui/alert/alert-title.svelte",
"type": "registry:ui"
},
{
"path": "ui/alert/alert.svelte",
"type": "registry:ui"
},
{
"path": "ui/alert/index.ts",
"type": "registry:ui"
}
]
},
{
"name": "alert-dialog",
"type": "registry:ui",
"dependencies": [
"bits-ui"
],
"registryDependencies": [
"button"
],
"files": [
{
"path": "ui/alert-dialog/alert-dialog-action.svelte",
"type": "registry:ui"
},
{
"path": "ui/alert-dialog/alert-dialog-cancel.svelte",
"type": "registry:ui"
},
{
"path": "ui/alert-dialog/alert-dialog-content.svelte",
"type": "registry:ui"
},
{
"path": "ui/alert-dialog/ale
....

[ieedan]

I didn't expect that to work!

I'll take a closer look now

[ieedan]

You've also tried it without the proxy right?

[Kaidstor]

yep, i publish repo https://github.com/Kaidstor/psqlgui

[Kaidstor]

i try to create new app and get same error it doesn't matter on what project i work

[ieedan]

Working on trying to expose the error right now

[ieedan]

Ah wait... try:

curl https://huntabyte-next.shadcn-svelte.pages.dev/registry/index.json

Forgot the registry is still being rewritten to here

[Kaidstor]

curl https://huntabyte-next.shadcn-svelte.pages.dev/registry/index.json
[
{
"name": "accordion",
"type": "registry:ui",
"dependencies": [
"bits-ui"
],
"registryDependencies": [],
"files": [
{
"path": "ui/accordion/accordion-content.svelte",
"type": "registry:ui"
},
{
"path": "ui/accordion/accordion-item.svelte",
"type": "registry:ui"
},
{
"path": "ui/accordion/accordion-trigger.svelte",
"type": "registry:ui"
},
{
"path": "ui/accordion/index.ts",
"type": "registry:ui"
}
]
},
{
"name": "alert",
"type": "registry:ui",
"dependencies": [
"bits-ui"
],
"registryDependencies": [],
"files": [
{
"path": "ui/alert/alert-desc
....

[Kaidstor]

upd it in components.json

		"hooks": "$lib/hooks"
	},
	"typescript": true,
	"registry": "https://huntabyte-next.shadcn-svelte.pages.dev/registry"
}

not help to init

│
◐  Initializing project...│
└  [CLI Error]: Failed to fetch base color from registry.

[ieedan]

it is currently automatically doing it so no need to update it in your components.json

[Kaidstor]

if i rm components.json and start bun x shadcn-svelte@next init

then get components.json

{
	"$schema": "https://next.shadcn-svelte.com/schema.json",
	"style": "default",
	"tailwind": {
		"config": "tailwind.config.js",
		"css": "src/app.css",
		"baseColor": "stone"
	},
	"aliases": {
		"components": "$lib/components",
		"utils": "$lib/utils",
		"ui": "$lib/components/ui",
		"hooks": "$lib/hooks"
	},
	"typescript": true,
	"registry": "https://next.shadcn-svelte.com/registry"
}

[ieedan]

I was assuming this was a work setting. It's not making sense right now.

Worth noting that #1726 could be related.

[Kaidstor]

maybe, i try to use all proxies that i has de, nl, ru, kz, etc.. if some will work told u

[Kaidstor]

try 10 different countries..

psqlgui on  main [!?] is 📦 v0.1.0 via 🥟 v1.2.4 via ⬢ v22.13.1
❯ bun x shadcn-svelte@next add button
┌ shadcn-svelte v1.0.0-next.6
│
▲ Incompatible dependency versions detected:
│
│ need tailwindcss@3.x.x >> found 4.0.12
│
│ Use at your own risk!
│
└ [CLI Error]: Failed to fetch components from registry.

psqlgui on  main [!?] is 📦 v0.1.0 via 🥟 v1.2.4 via ⬢ v22.13.1 took 12s
❯ curl -s https://ipinfo.io
{
"ip": "46...~~",
"city": "New York City",
"region": "New York",
"country": "US",
"loc": "40.7152,-73.9877",
"org": "AS62240 Clouvider",
"postal": "10002",
"timezone": "America/New_York",
"readme": "https://ipinfo.io/missingauth"
}%

US doesn't work too..

[ieedan]

Try this for the full error

// try commenting or uncommenting this to see if it's a problem with this fetch implementation
import { fetch } from "node-fetch-native";

const response = await fetch("https://huntabyte-next.shadcn-svelte.pages.dev/registry/index.json");

// you probably won't even make it here since it is giving fetch failed
console.log(response);

[laith43d]

Try this for the full error

// try commenting or uncommenting this to see if it's a problem with this fetch implementation
import { fetch } from "node-fetch-native";

const response = await fetch("https://huntabyte-next.shadcn-svelte.pages.dev/registry/index.json");

// you probably won't even make it here since it is giving fetch failed
console.log(response);

this actually fetched the registry/index.json successfully for me, however the command still fails:

pnpm start add accordion --cwd ../../../qreverything/
┌   shadcn-svelte  v1.0.0-next.6 
│
└  [CLI Error]: Failed to fetch registry from https://huntabyte-next.shadcn-svelte.pages.dev/registry. Error: TypeError: fetch failed

 ELIFECYCLE  Command failed with exit code 1.
`

can add the component manually? is there any configuration I need to update if I add it manually?

[ieedan]

I still haven't been able to reproduce through all of this maybe you both have something common in your environment...

[ieedan]

Looking at the OP of the other issue I don't see anything in common for the system stat command.

[laith43d]

when I run this command:

pnpm dlx shadcn-svelte@next add accordion

I get this error:

┌   shadcn-svelte  v1.0.0-next.6 
│
└  [CLI Error]: Failed to fetch components from registry.

about an hour ago I was getting a different error which is:

pnpm dlx shadcn-svelte@next add accordion
 WARN  GET https://registry.npmjs.org/shadcn-svelte error (UNABLE_TO_GET_ISSUER_CERT_LOCALLY). Will retry in 10 seconds. 2 retries left.

I bypassed that with:

pnpm config set strict-ssl false

[laith43d]

ISSUE RESOLVED: A TLS Comedy of Errors

Ah, the classic "it was something obvious all along" moment! After some delightful troubleshooting, I’ve uncovered the culprit behind our woes:

During a routine brew upgrade, OpenSSL was bumped from 1.1 to 3.x. Little did I know this would trigger a chain reaction:

• macOS’s TLS validation suddenly developed a case of the "I can’t find my certificates" blues
• npm/pnpm started throwing errors like a toddler whose lollipop was taken away
• all my applications auth routines suddenly stoped working!

The root cause? OpenSSL 3.x moved its root certificates to a new path, and macOS obviously decided this was the perfect time to test my debugging skills. (Why yes, I did facepalm. Several times.)

The Fix (aka How I Restored Order to the Universe):
Adding this line to my .zshrc reconnected the certificate dots:

export NODE_EXTRA_CA_CERTS="/opt/homebrew/etc/ca-certificates/cert.pem"  

Post-Resolution Reflection:
Turns out, my system was just reminding me that "if it’s not broken, upgrade it anyway" is a developer’s mantra for a reason. 🚀

Special thanks to past-me for forgetting they’d hardcoded an ancient certificate path—because nothing says "fun" like debugging a problem caused by your own 6-month-old self!

[Kaidstor]

add your extra and get

┌ shadcn-svelte v1.0.0-next.7
│
▲ Incompatible dependency versions detected:
│
│ need tailwindcss@3.x.x >> found 4.0.12
│
│ Use at your own risk!
│
└ [CLI Error]: Failed to fetch registry from https://23f7e4d7.shadcn-svelte.pages.dev/registry. Error: TypeError: fetch failed

[tolstovrob]

Keep facing same issue after 2 days of attempting. Tried everything but it didn't work out. I was using yarn.

But it works for yarn dlx shadcn-svelte. Is it crucial to determine the version like shadcn-svelte@next?

[MCMattia]

For me the problem is that the company PC block all websites with url pages.dev. Since it's very easy to create a website with this domain provided by cloudflare it's blocked by the firewall. Could it be possible to use a url like next.shadcn-svelte.com/registry?

Error:
Failed to fetch base color from registry. Error: CLI Error: Failed to fetch registry from https://huntabyte-next.shadcn-svelte.pages.dev/registry. Error: TypeError: fetch failed

[nikitaiavdeev]

For me it was a network issue at my company caused by SSL at CLI url.

I changed this parameter temporarily and it solved an issue

pnpm config set strict-ssl false
npm config set strict-ssl false
set NODE_TLS_REJECT_UNAUTHORIZED = 0

[tolstovrob]

Btw, for me it was fixed by turning on VPN. Maybe it's the way

[tim-lux]

Maybe helpful to someone: I used VSCodium's built-in terminal and it failed, using my native Linux terminal worked.
(I had the same issue with https://tw3.shadcn-svelte.com/registry/default/styles/vega/index.json: 404 Not Found)