shadcn.io is not affiliated with official shadcn/ui
Missing Dependency Error Block for React
A full-screen page for a missing package: the error line in a copy strip, four install tabs with real Copy buttons, the package card and three steps for after installing.
Installation
Overview
Name the package and hand over the command, with this missing dependency error for React with Base UI. It's a whole screen with the page's rails and one band across it. The headline, one sentence and the Shine Button Open the docs come first, the only colored control. Under them the line the build printed sits in a strip with a heavy edge and a Copy Button. In an inset frame, four Tabs for npm, yarn, pnpm and bun each hold the install command in a themed numbered window whose Copy button really copies it. Two cells on a shared hairline hold the package card, with its name, version and one line, and the three steps to take after installing. The band's rules and the frame come from Guides, and the entrance is CSS only. For a UI library, a CLI or any docs site that tells people to install something.
FAQ
What is real here, and what stays local?
The Copy buttons are real: each writes its text to the clipboard and the status line says what was copied. Nothing is installed or built. The package is made up for the demo and says so on its card, so swap the name, version and commands in PACKAGE, VERSION and MANAGERS for yours.
Is the package name safe to run?
No, and that is why it is marked as an example: a name that does not exist on a registry can be registered by anyone, so never paste a command from a demo into a real project. When you use the block, point it at a package you publish.
Does the page remember which tool I picked?
Only while it is open: the chosen tab is state in the page, and the status line says which command is showing. The tabs are a real tab list, so the arrow keys move between them, and each command window has its own tab stop and name.
Are the commands correct for each tool?
They are the usual forms: install for npm, add for yarn, pnpm and bun. If your package needs a flag or a peer dependency, add it to the command string; the window, the Copy button and the status all read the same string.
Related
- Pro
Missing API Key Error
Developer toolsA full-screen page for a developer whose API key is missing: the steps to fix it, and a numbered .env window whose empty key line is marked and can be filled with a sample key that shows as a diff.
- Pro
Invalid Config File Error
Developer toolsA full-screen page for a config file that does not validate: a numbered, editable JSON window parsed as you type, the problems located by line and column, and one button that applies the fixes.
- Pro
Failed Build Pipeline Error
Developer toolsA CI build window: five pipeline stages as tabs, each with its own numbered log, the failing line marked, a re-run that only queues, common fixes and the build id with Copy.
- Pro
CORS Blocked Request Error
NetworkA full-screen page for a cross-origin request the browser blocked: a drawn exchange with the reply's headers and the missing one dashed, the console line in a copy strip, and three fixes with snippets you can copy.
- Pro
Version Mismatch Ruler Error
MaintenanceA full-height page for a web app tab running a retired version: a ruler of five releases with the supported range shaded and You are here marked, a radio group to read each release, three changes in 5.0 and a reload button.
- Pro
Deploy Rolled Back Error
Developer toolsA full-screen page for a rolled-back deploy: a line chart of one metric against its limit with the health check, rollback and recovery pinned to it, and a switch between three metrics.