Shadcn add fails: v0 component ‘date-picker’ not found in registry

When attempting to add the v0 component https://v0.dev/chat/b/b_MDsFl9sNbn4 using npx shadcn@latest add, the command fails with a 404 error:

Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

The component at https://ui.shadcn.com/r/styles/new-york-v4/date-picker.json was not found.
It may not exist at the registry. Please make sure it is a valid component.

This occurs because the v0 component appears to have an invalid dependency declared (pointing to date-picker.json), which doesn’t exist in the official shadcn/ui registry, as the Date Picker is meant to be composed manually.

Expected behavior:
Ideally, the shadcn add command should either:
a) Successfully install the v0 component if its dependencies are valid and exist.

b) Provide a more informative error indicating that a dependency is pointing to a non-existent registry component.

c) Potentially handle the composition automatically if the intent is clear.

Steps to Reproduce:

  1. Initialize a new Next.js 15 project with TypeScript, Tailwind CSS v4, and the App Router.

  2. Initialize shadcn-ui using the latest CLI and install:
    npx shadcn@2.3.0 add “https://v0.dev/chat/b/tC1vh0bPZI3

  • Relevant components.json settings after init:

  • Style: default

  • Base Color: neutral

  • CSS Variables: yes

  • Using src directory.

  • Relevant dependencies (see Project Information below).

Project Information:

  • Framework: Next.js 15.3.1

  • Styling: Tailwind CSS v4 (using @tailwindcss/postcss)

  • Language: TypeScript

  • Key Dependencies:

  • React: 19.0.0

  • Environment:

  • OS: macOS (Darwin 24.4.0)

  • Package Manager: npm * shadcn/ui Settings: Default style, Neutral base color, using CSS variables, components installed in src/components/ui, utils in src/lib/utils.ts.

There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Maybe a version issue here. What happens if you use an older version, like npx shadcn@2.3.0 add... instead of latest?

➜ boxsy-debug git:(main) ✗ npx shadcn@2.3.0 add “https://v0.dev/chat/b/tC1vh0bPZI3
:check_mark: You need to create a components.json file to add components. Proceed? … yes
:check_mark: Which style would you like to use? › New York
:check_mark: Which color would you like to use as the base color? › Neutral
:check_mark: Would you like to use CSS variables for theming? … no / yes
:check_mark: Writing components.json.

It looks like you are using React 19.
Some packages may fail to install due to peer dependency issues in npm (see Next.js 15 + React 19 - shadcn/ui).

:check_mark: How would you like to proceed? › Use --legacy-peer-deps
⠙ Checking registry.

Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

The component at https://ui.shadcn.com/r/styles/new-york/date-picker.json was not found.
It may not exist at the registry. Please make sure it is a valid component.

Same issue.

It appears the use of date-picker.json is outdated and the component should instead be a combination of the Popover and the Calendar components [ref]

Please ask v0 to correct the code to make use of the current Date Picker component: Date Picker - shadcn/ui

I prompted v0 a few times to update the component and it has updated the code base but when forking the codebase to my IDE the same issue arises.

Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

The component at https://ui.shadcn.com/r/styles/new-york/date-picker.json was not found.
It may not exist at the registry. Please make sure it is a valid component.

Vercel v0 component I am trying to add (https://v0.dev/chat/b/b_iI01DGswwGr) appears to have a dependency on the old, deprecated date-picker component from the shadcn/ui registry.
As we established earlier, date-picker is no longer a standalone component installable via shadcn add by referencing date-picker.json. It needs to be manually constructed using Popover and Calendar. I did that in my codebase.

We have the same issue for the user-avatar. https://ui.shadcn.com/r/styles/new-york/user-avatar.json.

The only workaround I found was to download the zip file and export it to an empty codebase. I hope the Vercel team can fix the issue to ensure that v0 uses the latest documentation in parallel to make sure there is no version mismatch with Next, Tailwind and Shadcn.

I’m glad you have a workaround at least. Shared your feedback with the team :person_bowing:

This could be a Tailwind version compatibility issue. Can you try with Tailwind v3 instead of latest?

Same issue:
➜ boxsy-debug git:(main) ✗ npx shadcn@2.3.0 add “https://v0.dev/chat/b/b_2ubLoygkfox
:check_mark: You need to create a components.json file to add components. Proceed? … yes
:check_mark: Which style would you like to use? › New York
:check_mark: Which color would you like to use as the base color? › Neutral
:check_mark: Would you like to use CSS variables for theming? … no / yes
:check_mark: Writing components.json.

It looks like you are using React 19.
Some packages may fail to install due to peer dependency issues in npm (see Next.js 15 + React 19 - shadcn/ui).

:check_mark: How would you like to proceed? › Use --legacy-peer-deps
⠇ Checking registry.

Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

The component at https://ui.shadcn.com/r/styles/new-york/date-picker.json was not found.
It may not exist at the registry. Please make sure it is a valid component.

{
“name”: “boxsy-debug”,
“version”: “0.1.0”,
“private”: true,
“scripts”: {
“dev”: “next dev”,
“build”: “next build”,
“start”: “next start”,
“lint”: “next lint”
},
“dependencies”: {
“class-variance-authority”: “^0.7.1”,
“clsx”: “^2.1.1”,
“lucide-react”: “^0.506.0”,
“next”: “15.3.1”,
“react”: “^19.0.0”,
“react-dom”: “^19.0.0”,
“tailwind-merge”: “^3.2.0”,
“tailwindcss-animate”: “^1.0.7”
},
“devDependencies”: {
@eslint/eslintrc”: “^3”,
@types/node”: “^20”,
@types/react”: “^19”,
@types/react-dom”: “^19”,
“autoprefixer”: “^10.4.21”,
“eslint”: “^9”,
“eslint-config-next”: “15.3.1”,
“postcss”: “^8.5.3”,
“tailwindcss”: “^3.4.17”,
“typescript”: “^5”
}
}

Thanks for confirming. I have an internal ticket with the v0 team to get this fixed.

In the meantime, you may be able to work around this by manually replacing the missing date picker component with the popover and calendar components as shown in the docs

2 Likes