Forms

Date Picker

A calendar date picker using react-day-picker with portal rendering, custom format strings, and clear button.

Quick Preview

Appointment Date

Installation

npm install react-day-picker date-fns

// Copy DatePicker.tsx to your components/forms/ folder
// src/components/forms/DatePicker.tsx

Usage

import { DatePicker } from '@/components/forms/DatePicker'

const [date, setDate] = useState<Date | undefined>()

<DatePicker
  value={date}
  onChange={setDate}
  label="Date"
  placeholder="Pick a date"
  formatStr="PPP"        // e.g. "January 1st, 2025"
/>

Examples

Disabled state

Disabled

Custom format

Short format (dd/MM/yyyy)

Prompt Preview

Copy a prompt that recreates this UI

Paste this into your AI coding assistant to generate code that closely matches the reference, including color, size, shape, typography, spacing, and polish.

Copy-ready AI prompt

Starts from the current visual reference and project constraints.

Build a forms component named Date Picker in React/Next.js.
Goal: recreate the same overall UI and behavior as the Date Picker reference from a component gallery.
What it needs to communicate: A calendar date picker using react-day-picker with portal rendering, custom format strings, and clear button..

Project constraints:
- Use Next.js 16.2.6 with the App Router, React 19, TypeScript strict mode, and Tailwind CSS v4.
- Do not create a tailwind.config.js file. Use Tailwind v4 utilities and CSS variables where design tokens are needed.
- If you are implementing this inside the same project, use the Prompt font via next/font/google. If not, use the closest equivalent typeface.
- Return production-ready code with imports, responsive behavior, keyboard accessibility, and polished empty, hover, focus, active, and disabled states where relevant.
- Match the reference closely: color palette, spacing scale, border radius, shadows, icon scale, typography hierarchy, and motion timing.

Component-specific expectations:
- Support label, helper, error, disabled, and validation states.
- Ensure keyboard usability and accessible form semantics.
- Avoid unnecessary dependencies unless the behavior truly requires them.
- No explicit color literals were found in the examples. Match the live reference and the project accent color when appropriate.

Props to support:
- value: Date | undefined — Controlled selected date
- onChange: (date: Date | undefined) => void — Called when date changes
- placeholder: string — default "Pick a date" — Trigger placeholder
- disabled: boolean — default false — Disables the picker
- label: string — Label above the trigger
- formatStr: string — default "PPP" — date-fns format string for display

Reference usage patterns:
- No examples were documented. Infer a sensible default presentation and one richer usage example.

Feature expectations:
- Calendar popup via react-day-picker
- Portal rendering (never clipped by overflow)
- Custom date format strings (date-fns)
- Clear button to reset date
- Disabled state
- Primary color selected day styling

Output requirements:
- Return complete code, not pseudocode.
- Include all necessary imports and helper types.
- Keep the implementation accessible, responsive, and visually finished.
- Match the reference for color, size, shape, typography, spacing, and interaction states as closely as possible.
- If multiple files are needed, organize them cleanly and explain the file structure briefly.

Tweak only product-specific copy or data after the first generation pass.

Props

Prop	Type	Default	Description
`value`	`Date \| undefined`	-	Controlled selected date
`onChange`	`(date: Date \| undefined) => void`	-	Called when date changes
`placeholder`	`string`	`"Pick a date"`	Trigger placeholder text
`disabled`	`boolean`	`false`	Disables the picker
`label`	`string`	-	Label rendered above trigger
`formatStr`	`string`	`"PPP"`	date-fns format string for display

← Back to Forms