Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

No Logs Empty State Block for React

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.

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 log console into the first line, with this no logs empty state for React with Base UI. A hairline frame with a plus mark on each corner holds the console of Cordwood, a log service, as a window of one fixed height with no sidebar: a top bar with the page's name and the Shine Button, the only colored control, Send a test line. Under it a drawing of the pipe (your app, a pipe, the console), dashed while nothing flows, and a bar of four level chips, Toggle Group items for Debug, Info, Warn and Error with their counts, beside a Switch that follows the newest line. The console is a log that is dark by nature, as terminals are, with the empty message in it. Each press prints the next typed line at its fixed time and the pipe turns solid; the chips hide and show lines by level. The window never changes size, and everything moves with CSS only. For the empty state of any log, trace or event viewer.

FAQ

Where do the lines come from, and how do I make it real?

Nothing is logged or sent. The twelve lines are typed in the page, each with its fixed time, and each press prints the next in order; a Clear button, quiet until there is a line, starts again. To wire it for real, stream the lines your API returns into the console where the code says so and compute the chips' counts from them.

Do the level chips really filter?

Yes. They are a group of toggle buttons: pressing one hides or shows the lines of that level, every chip keeps its count of what has come in, and the foot says how many lines are shown. With every level off the console says "No lines match" in place instead of going blank. The window keeps its height throughout.

What does Follow do?

While it is on, each new line scrolls the console to the newest one, inside the console only, never the page. Turn it off to read earlier lines while more arrive; turning it on again jumps back to the end. The scrolling console is a labelled region that takes focus, so arrow keys scroll it.

Why is the console dark in a light theme?

Terminals and logs are dark by nature, so the console carries its own dark scope while the window around it follows the theme (a code comment says so). Levels are told apart by their word, weight and a bar at the start of the line, never by color alone.

How does it look on a phone?

The window keeps its height, the chips scroll sideways inside their own row so the page never does, and the product name and the pipe's captions drop out. The button stays in the top bar and the console scrolls inside itself.

Is the console accessible?

The log is a named region of real text with its times in <code>time</code> elements, and it does not announce each line (a busy log would drown everything else); the foot's polite line says what a press printed. The chips and the switch are named, and the pipe is hidden from assistive technology.

  • Pro

    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.

  • 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.

  • Pro

    An uptime monitor's empty list as a setup form: an address, a check interval, three regions and a derived checks-a-day line, a flat heartbeat line with a dashed first spike, and one Add monitor button with a simulated check.

  • Pro

    A performance monitor's empty dashboard as the target before the data: tabs for four metrics, a chart of axes with a dashed flat line and target band, a slider that moves the target, a strip of four targets and one Set up monitoring button.

  • Pro

    Build Passed Success

    Builds and deploys

    A confirmation window for a green build: a bar of four stages as wide as their share of the run, a typed terminal log for the chosen stage with a once-only replay, a small artifacts table and a local Deploy this build.

  • 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.