Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

No Error Tracking Empty State Block for React

An error monitor's empty list as an install guide: a code window with npm, pnpm and bun tabs and a copy button, an initialise snippet, a Send a test error button that lists one simulated row, and a calm lake whose ring turns solid.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

Turn an empty error list into the three steps that fill it, with this no error tracking empty state for React with Base UI. The page is Snagless, an error monitor: the rails of the page and one band across it are split in two. At the start the heading, one sentence and three steps. First a code window with Tabs for npm, pnpm and bun and a Copy Button for the command of the open tab. Second a code window with the initialise snippet. Third a Send a test error button that lists one simulated row. Under them the Shine Button, the only colored control, Copy install command. At the end a calm lake with one still boat, whose ring on the water is dashed until an error has come in and solid after it. The frame is ruled by Guides, the lake is one SVG whose classes change, and everything moves with CSS only. For the first screen of any error, log or performance tool.

FAQ

What stays in the page, and how do I make it real?

No SDK is loaded and nothing is sent. The package and host names are made up, and the test error is a row kept in the page's state: each press adds one to "Seen 3 times" and a reload clears it. To wire it for real, use your own package and key in both snippets, capture a real error where the code says so, and list what your API returns here instead of the typed row.

What do the two copy buttons do?

The small button in the code window copies the command of the open tab, and the Shine Button under the steps does the same: both write the same text to your clipboard, which is the one thing here that really leaves the page. The polite line under the steps says which command was copied ("Copied the pnpm command.") or that the clipboard refused it, with a note to copy it by hand.

How do the tabs work?

Each tab shows one package manager's command, in a window of one fixed height, so choosing a tab never moves the page. They are real tabs, so the arrow keys move between them and Tab goes on to the copy button and the command itself, which scrolls sideways inside its window on a narrow screen. The code windows follow the theme; only a real terminal would stay dark.

What does Send a test error do?

It lists one row, "TestError: demo error from this page", with how many times it was seen and the page's fixed date, turns the ring around the boat solid and adds a wider ring. The slot holds one row's height before and after, so nothing moves. Start over, which stays quiet until there is a row, clears it and puts focus back on the button.

Is the lake anything but decoration?

No. It is hidden from assistive technology; the same facts are in the list's row ("No errors captured yet" or the test error) and in the status line. The ring is dashed while the water is still and its change is a CSS transition that is off under reduced motion.

How does it look on a phone?

The lake sits above the copy at 112 px tall, the steps stack, and the copy button is pinned to the foot of the screen while the page is in view so it is always in reach. Nothing scrolls sideways, even at 320 px wide; the code scrolls inside its window.

  • Pro

    An ops status board's quiet alerts page: a bell under a glass dome, four systems that each say Operational with a drawn 30-day strip, and a Send a test alert button that fills a dashed slot with a typed row you can dismiss.

  • Pro

    No Logs Empty State

    Developer tools

    A log console window with nothing logged yet: a dashed pipe from an app to a console, four level chips with counts, a Follow switch, a dark console and one Send a test line button that prints the next of twelve typed lines.

  • Pro

    An incident tracker's quiet log: a calendar of 13 weeks of 7 quiet dots, a 30, 60 or 90 day range that re-slices the grid and the line 0 incidents in 60 days, and a Run a drill button that marks one day with a tooltip.

  • Pro

    A code scanner's clean results page as a scan scope: four areas with an Include switch each, a Run scan that walks through them in a simulated scan and ends on 0 found, and a shield whose dashed check turns solid.

  • Pro

    An API platform's first-key page as a split screen: a name, a scope and one Create key button that shows a made-up demo key once with a copy button, then masks it into a one-row list with Revoke, while a drawn gate takes its pin.

  • Pro

    A deploy platform's first-deployment page as a split screen: an environment, a Skip tests switch and a dark terminal whose command follows them, one Copy command button, and a sample run that lists a first deployment while a drawn balloon fills.