Measured entry
shadcn-block-calendar-01
A client-side React single-date calendar example shipped as a shadcn registry block. It wraps the shared Calendar and Button components built on react-day-picker, with date-fns, Lucide icons, Radix Slot, Tailwind theme classes, and the shadcn cn utility in the dependency chain.



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 | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 50.8 KB (116.2 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | none |
What the harness recorded
BARE BUILD
✗ Build failed in 34.03s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/calendar.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A solid fit inside an existing shadcn application: it builds, mounts, stays contained across the tested layouts, and passed the accessibility scan. It is not drop-in for a bare React app and needs a shadcn-style setup, including shared utilities and primitives.
Use it if
- You need an inline single-date picker with controlled React state.
- Your app already uses shadcn conventions, Tailwind theme tokens, and shared Button primitives.
- You want a react-day-picker base that can later support ranges, disabled dates, or custom captions.
Skip it if
- A native date input is sufficient and adding a calendar library would be unnecessary.
- Your project does not use Tailwind or shadcn theme tokens and you do not want to translate its styling.
- You need scheduling, time selection, events, or form validation without building that behavior around this picker.
- Your dependency budget is tight for a single-date control.
Install
| Declared dependencies | react-day-picker@latest, date-fns, @radix-ui/react-slot |
|---|---|
| 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 |
In a non-shadcn project, add react-day-picker, date-fns, Lucide React, Radix Slot, the shared Button primitive, a class-name merge helper matching cn, and Tailwind styles that define the referenced theme tokens. Update the registry aliases to your local paths and ensure the file runs as a client 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/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-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
- shadcn-block-calendar-06minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 50.9KB
- Bare
- fail
- Prov
- NO