Measured entry
shadcn-block-calendar-12
A client-side appointment date-range calendar with an English and Spanish language switcher, localized labels, and internal React state. It ships as a shadcn registry block composed from Calendar, Card, and Select components, backed by React Day Picker, date-fns, and Radix primitives.



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.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 1 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 82.9 KB (148.3 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | none |
What the harness recorded
BARE BUILD
✗ Build failed in 40.22s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/card.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
It builds and mounts in the prepared harness, but the unnamed calendar button is an accessibility release blocker. It also needs a shadcn-style setup and carries a sizable date-picker footprint, so use it as a starting block rather than a drop-in booking feature.
Use it if
- You need a date-range appointment picker with English and Spanish copy already wired together.
- Your app already uses shadcn component conventions, aliases, utility classes, and registry primitives.
- You want the chosen range managed locally and can connect it to your own booking flow.
Skip it if
- You need a drop-in component for a plain React project with no shadcn foundation.
- Your release cannot accept an unnamed calendar button until its accessible name is fixed.
- You need server-owned selection state, availability rules, time slots, or booking submission out of the box.
- You are minimizing client bundle cost and do not otherwise need a full date-picker stack.
Install
| Declared dependencies | react-day-picker@latest, date-fns, @radix-ui/react-slot, @radix-ui/react-select |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
A non-shadcn project must add the source alias, the shared class-name utility, Tailwind theme and component styles, and compatible Calendar, Card, and Select implementations. It must also install React Day Picker, date-fns, Radix Slot, and Radix Select, then give every calendar button an accessible name.
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/shadcn-ui/uiAlternatives
Other published entries for the calendar pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- shadcn-calendarunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 37.3KB
- Bare
- fail
- Prov
- NO
- shadcn-block-calendar-01minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 50.8KB
- Bare
- fail
- Prov
- NO
- shadcn-block-calendar-02minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 50.9KB
- Bare
- fail
- Prov
- NO
- shadcn-block-calendar-03minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 50.9KB
- Bare
- fail
- Prov
- NO
- shadcn-block-calendar-04minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 50.9KB
- Bare
- fail
- Prov
- NO
- shadcn-block-calendar-05minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 50.9KB
- Bare
- fail
- Prov
- NO