vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-navbar-status

navbarunclassified

A prop-driven Next.js client navbar that pairs logo and navigation links with service status, uptime, and latency. It ships as shadcn registry source copied into your app and depends on Next Link, Lucide icons, Tailwind utility classes, semantic theme tokens, and the customary cn helper.

Specimen
Harness screenshot of ruixen-navbar-status at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-navbar-status at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-navbar-status at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

Measured

Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.

Harness measurements recorded for ruixen-navbar-status
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal43.3 KB (108.7 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 47.62s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/navbar-status.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A sensible, restrained choice for a status-aware dashboard shell, with clean responsive behavior and a small prop surface. It needs a shadcn-style setup to mount as written, and teams should plan a separate mobile navigation pattern.

Use it if

  • You need a compact dashboard header that keeps service status visible on narrow screens.
  • Your product already uses Next.js, Tailwind, and shadcn-style theme conventions.
  • Your navigation, status label, and operational metrics can be supplied through simple props.

Skip it if

  • Mobile users must retain access to the navigation links or operational metrics, since both are hidden on narrow screens.
  • You need a framework-neutral navbar without a Next Link dependency.
  • Status changes must be announced live to assistive technology without further accessibility work.

Install

Installation record for ruixen-navbar-status
Declared dependencieslucide-react
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

A non-shadcn project must add Tailwind theme tokens, configure the at-sign import alias, provide a lib/utils module exporting cn, and install Lucide React. It must also use Next.js or replace Next Link with the project's router link component.

Source and credit

This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.

Author repository

github.com/ruixenui/ruixen.com
License
MIT
Record published
2026-08-14

Alternatives

Other published entries for the navbar pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.