Measured entry

ruixen-deploy-region-globe

globe-vizspatialmotion on file

A client-side deployment-region card that pairs a Cobe canvas globe with an expandable region picker, latency caption, and confirmation callback. It ships as a shadcn registry TSX component and relies on React, Cobe, Lucide icons, next-themes, a cn helper, and Tailwind theme tokens.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of ruixen-deploy-region-globe at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-deploy-region-globe at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-deploy-region-globe 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-deploy-region-globe
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical2
Axe serious2
Axe moderate0
Axe minor0
Gzip marginal35.7 KB (101.1 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 41.83s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/deploy-region-globe.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A polished, focused region picker with useful customization hooks, but it is not drop-in outside its native ecosystem. It needs a shadcn-style setup, and the current ARIA structure, list semantics, and contrast issues should be fixed before production use.

Use it if

  • You need a region selector that visually connects each option to a globe location.
  • Your product already uses shadcn conventions, Tailwind theme tokens, and next-themes.
  • You can supply real region coordinates and latency data through the component props.
  • You want selection and confirmation callbacks instead of bundled deployment logic.

Skip it if

  • You need an accessible component without first repairing the listbox structure, list semantics, and contrast.
  • A lightweight native select is more appropriate than adding a WebGL globe dependency.
  • Your app cannot rely on browser canvas, ResizeObserver, or client-side rendering.
  • You need live latency measurement or deployment behavior, since this component only displays supplied data and emits callbacks.

Install

Installation record for ruixen-deploy-region-globe
Declared dependenciescobe, lucide-react
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 Cobe, Lucide React, and next-themes; provide the cn class-merging helper; configure Tailwind with the referenced semantic color and focus-ring tokens; and place the component behind a client boundary. Add a theme provider if your app needs its light and dark globe treatments.

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.

Alternatives

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