vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-navbar-with-search

navbarunclassified

A client-side Next.js header with a logo link, desktop navigation, a search field, a visual shortcut hint, and an optional action area. It ships as a shadcn registry component and relies on React, Next Link, lucide-react, Tailwind theme classes, the cn utility, and a registry Button backed by the declared UI dependencies.

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

Verdict

A sensible starting point for an app header, but it is desktop-oriented and leaves search semantics, shortcut behavior, and mobile navigation to the adopter. It needs a shadcn-style setup to build and mount, and the flagged contrast should be fixed before shipping.

Use it if

  • You need a compact desktop header whose links, logo, search callback, placeholder, and actions are supplied as props.
  • Your app already uses Next.js and a shadcn-style Tailwind component setup.
  • You want search input changes reported immediately and will implement the actual search behavior elsewhere.

Skip it if

  • Mobile users must have access to navigation or search, since both are hidden on smaller screens with no menu replacement.
  • You need a working keyboard shortcut, since the shortcut badge is only visual and has no key handler.
  • You cannot remediate the detected text contrast issue before release.
  • Your project is not based on Next.js and you do not want to replace its Link usage or recreate shadcn utilities.

Install

Installation record for ruixen-navbar-with-search
Declared dependencieslucide-react, radix-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 lucide-react and the declared UI dependency, provide Tailwind with matching theme tokens, a cn class-merging utility, and a compatible Button component. Use Next.js for Link or replace it with your router, and add the client-component boundary where your framework requires one.

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.