Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Failed Build Pipeline Error Block for React

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

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

Show a failed build the way a developer reads it, with this build error window for React with Base UI. It's an app window in a fixed-height frame on plus-marked corners. The top bar holds the heading and the one Shine Button, Re-run from Typecheck. Under it are the build's facts with its id and a Copy Button, then the pipeline as five Tabs across: Install and Lint done, Typecheck failed, Build and Deploy skipped, each with a shape and a word rather than a color. Typecheck is open on load, and its log is a themed numbered window with the time into the stage, the failing lines marked by a heavy edge and the word failed. The foot has a Common fixes disclosure that opens over the foot of the log so nothing moves, an Undo for the queued run and a link to the full log. The frame's corners come from Guides, and the entrance is CSS only. For a CI service, a deploy dashboard or any pipeline view.

FAQ

What is real here, and what stays local?

Re-run only queues in the page and says so: nothing is built, and the logs are typed sample lines in the file. Copy build id really writes the id to the clipboard. To wire it for real, replace the STAGES array with your pipeline's stages and log lines, send Re-run to your CI's API, and point Open full log at your log page.

How do I tell which stage failed without color?

Each stage's tab says its state in a shape and a word: a check and Done, a cross and Failed, a dash and Skipped. The failed stage's cross is the one status color on the page, and its tab is the one open on load. In the log, the failing lines have a heavy edge at their start and a failed label.

How does the keyboard work?

Tab reaches Re-run, Copy build id, the stage tabs, the log (it is a scroll region with a tab stop and a name), Common fixes, Undo and the log link, in that order. The arrow keys move along the stage tabs. The window never changes height: only the log scrolls, sideways for a long line and up and down for a long stage.

Why does Common fixes open over the log instead of pushing it?

Because nothing in a window may move when you press something. The three fixes are a disclosure button with an expanded state, and their panel is drawn over the foot of the log, so the log lines and the foot stay where they are. Press the button again to close it.

Can I take back Re-run?

Yes. After Re-run the button reads Queued and the status says nothing ran; Undo is always there, quiet until a run is queued, and takes it back. Pressing a queued button again just says it is already queued.

What changes on a phone?

The button shortens to Re-run (its name stays Re-run from Typecheck), the stage tabs scroll sideways inside their row with the next one showing, and Open full log becomes an icon with the same name. The log scrolls inside itself, so the window keeps its height at 320 px.

  • Pro

    Failed Test Run Error

    Developer tools

    A test-runner window: a tree of suites and tests with their results, a Failed only switch, and a pane that compares expected and received values with the differing characters underlined.

  • Pro

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

  • Pro

    A debug-log viewer for an API monitoring tool, as a fixed-height app window: a Critical badge and copyable error id, a level filter with counts, eight log lines with the failing one marked, and a foot that copies, downloads and reports.

  • Pro

    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.

  • Pro

    A 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

    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.