vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-navbar-split

navbarunclassified

A static split navigation header that places configurable links on either side of a logo and keeps a call-to-action visible on smaller screens. It ships as a client-side shadcn registry component and depends on React, Next.js Link, Tailwind utility classes, the shadcn Button primitive, the cn helper, and the declared Radix package.

Specimen
Harness screenshot of ruixen-navbar-split at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-navbar-split at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-navbar-split 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-split
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate1
Axe minor0
Gzip marginal44.3 KB (109.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 53.08s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/navbar-split.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A clean fit for a simple Next.js product header, but incomplete as the sole navigation on mobile and worth fixing with distinct labels for its navigation landmarks. It needs a shadcn-style setup and does not work as a bare drop-in.

Use it if

  • You need a compact product header with separate primary and support link groups.
  • Your Next.js app already uses shadcn conventions, Tailwind utilities, and the shared Button component.
  • A desktop link bar with only a logo and call-to-action on smaller screens matches your navigation plan.

Skip it if

  • Mobile visitors must be able to reach every navigation link, since this component hides both link groups without providing a menu.
  • You need dropdowns, account controls, search, or other interactive navigation behavior.
  • Your page already has unlabeled navigation landmarks and you cannot add distinct accessible labels.
  • You want a framework-neutral component without Next.js and shadcn project conventions.

Install

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

In a non-shadcn project, add React, Next.js routing or replace Link with your router or anchors, configure Tailwind-compatible theme classes, install the declared Radix package, and provide equivalents for the Button component and cn utility. Add distinct accessible labels to the two navigation regions.

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.