Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

react-datetime

arqex1.1mMIT3.3.1TypeScript support: included

A lightweight but complete datetime picker React.js component

react, react-component, datepicker, timepicker, datetimepicker, datetime

readme

react-datetime

Build Status npm version

A date and time picker in the same React.js component. It can be used as a datepicker, timepicker or both at the same time. It is highly customizable and it even allows to edit date's milliseconds.

Back to the roots! Thanks to the people of YouCanBook.me (best scheduling tool) for sponsoring react-datetime for so long. Now the project returns to the community and we are looking for contributors to continue improving react-datetime. Would you like to give a hand?

Version 3 is out! These are the docs for version 3 of the library. If you are still using the deprecated v2, here it is its documentation, but we strongly recommend to migrate to version 3 in order to keep receiving updates. Please check migrating react-datetime to version 3 to safely update your app.

Installation

Install using npm:

npm install --save react-datetime

Install using yarn:

yarn add react-datetime

Usage

React.js and Moment.js are peer dependencies for react-datetime (as well as Moment.js timezones if you want to use the displayTimeZone prop). These dependencies are not installed along with react-datetime automatically, but your project needs to have them installed in order to make the datepicker work. You can then use the datepicker like in the example below.

// Import the library
import Datetime from 'react-datetime';

// return it from your components
return <Datetime />;

See this example working.

Do you want more examples? Have a look at our resources gallery.

Don't forget to add the CSS stylesheet to make it work out of the box.. You only need to do this once in your app:

import "react-datetime/css/react-datetime.css";

API

Below we have all the props that we can use with the <DateTime> component. There are also some methods that can be used imperatively.

Name Type Default Description
value Date new Date() Represents the selected date by the component, in order to use it as a controlled component. This prop is parsed by Moment.js, so it is possible to use a date string or a moment object.
initialValue Date new Date() Represents the selected date for the component to use it as a uncontrolled component. This prop is parsed by Moment.js, so it is possible to use a date string or a moment object. If you need to set the selected date programmatically after the picker is initialized, please use the value prop instead.
initialViewDate Date new Date() Define the month/year/decade/time which is viewed on opening the calendar. This prop is parsed by Moment.js, so it is possible to use a date string or a moment object. If you want to set the view date after the component has been initialize see the imperative API.
initialViewMode string or number 'days' The default view to display when the picker is shown for the first time ('years', 'months', 'days', 'time'). If you want to set the view mode after the component has been initialize see the imperative API.
updateOnView string Intelligent guess By default we can navigate through years and months without actualling updating the selected date. Only when we get to one view called the "updating view", we make a selection there and the value gets updated, triggering an onChange event. By default the updating view will get guessed by using the dateFormat so if our dates only show months and never days, the update is done in the months view. If we set updateOnView="time" selecting a day will navigate to the time view. The time view always updates the selected date, never navigates. If closeOnSelect={ true }, making a selection in the view defined by updateOnView will close the calendar.
dateFormat boolean or string true Defines the format for the date. It accepts any Moment.js date format (not in localized format). If true the date will be displayed using the defaults for the current locale. If false the datepicker is disabled and the component can be used as timepicker, see available units docs.
timeFormat boolean or string true Defines the format for the time. It accepts any Moment.js time format (not in localized format). If true the time will be displayed using the defaults for the current locale. If false the timepicker is disabled and the component can be used as datepicker, see available units docs.
input boolean true Whether to show an input field to edit the date manually.
open boolean null Whether to open or close the picker. If not set react-datetime will open the datepicker on input focus and close it on click outside.
locale string null Manually set the locale for the react-datetime instance. Moment.js locale needs to be loaded to be used, see i18n docs.
utc boolean false When true, input time values will be interpreted as UTC (Zulu time) by Moment.js. Otherwise they will default to the user's local timezone.
displayTimeZone string null Needs moment's timezone available in your project. When specified, input time values will be displayed in the given time zone. Otherwise they will default to the user's local timezone (unless utc specified).
onChange function empty function Callback trigger when the date changes. The callback receives the selected moment object as only parameter, if the date in the input is valid. If the date in the input is not valid, the callback receives the value of the input (a string).
onOpen function empty function Callback trigger for when the user opens the datepicker.
onClose function empty function Callback trigger for when the calendar get closed. The callback receives the selected moment object as only parameter, if the date in the input is valid. If the date in the input is not valid, the callback returns the value in the input.
onNavigate function empty function Callback trigger when the view mode changes. The callback receives the selected view mode string (years, months, days or time) as only parameter.
onBeforeNavigate function ( nextView, currentView, viewDate ) => nextView Allows to intercept a change of the calendar view. The accepted function receives the view that it's supposed to navigate to, the view that is showing currently and the date currently shown in the view. Return a viewMode ( default ones are years, months, days or time) to navigate to it. If the function returns a "falsy" value, the navigation is stopped and we will remain in the current view.
onNavigateBack function empty function Callback trigger when the user navigates to the previous month, year or decade. The callback receives the amount and type ('month', 'year') as parameters.
onNavigateForward function empty function Callback trigger when the user navigates to the next month, year or decade. The callback receives the amount and type ('month', 'year') as parameters.
className string or string array '' Extra class name for the outermost markup element.
inputProps object undefined Defines additional attributes for the input element of the component. For example: onClick, placeholder, disabled, required, name and className (className sets the class attribute for the input element). See Customize the Input Appearance.
isValidDate function () => true Define the dates that can be selected. The function receives (currentDate, selectedDate) and shall return a true or false whether the currentDate is valid or not. See selectable dates.
renderInput function undefined Replace the rendering of the input element. The function has the following arguments: the default calculated props for the input, openCalendar (a function which opens the calendar) and closeCalendar (a function which closes the calendar). Must return a React component or null. See Customize the Input Appearance.
renderView function (viewMode, renderDefault) => renderDefault() Customize the way the calendar is rendered. The accepted function receives the type of the view it's going to be rendered 'years', 'months', 'days', 'time' and a function to render the default view of react-datetime, this way it's possible to wrap the original view adding our own markup or override it completely with our own code. See Customize the Datepicker Appearance.
renderDay function DOM.td(day) Customize the way that the days are shown in the daypicker. The accepted function has the selectedDate, the current date and the default calculated props for the cell, and must return a React component. See Customize the Datepicker Appearance.
renderMonth function DOM.td(month) Customize the way that the months are shown in the monthpicker. The accepted function has the selectedDate, the current date and the default calculated props for the cell, the month and the year to be shown, and must return a React component. See Customize the Datepicker Appearance.
renderYear function DOM.td(year) Customize the way that the years are shown in the year picker. The accepted function has the selectedDate, the current date and the default calculated props for the cell, the year to be shown, and must return a React component. See Customize the Datepicker Appearance.
strictParsing boolean true Whether to use Moment.js's strict parsing when parsing input.
closeOnSelect boolean false When true, once the day has been selected, the datepicker will be automatically closed.
closeOnTab boolean true When true and the input is focused, pressing the tab key will close the datepicker.
timeConstraints object null Add some constraints to the timepicker. It accepts an object with the format { hours: { min: 9, max: 15, step: 2 }}, this example means the hours can't be lower than 9 and higher than 15, and it will change adding or subtracting 2 hours everytime the buttons are clicked. The constraints can be added to the hours, minutes, seconds and milliseconds.
closeOnClickOutside boolean true When the calendar is open and closeOnClickOutside is true (its default value), clickin outside of the calendar or input closes the calendar. If false the calendar stays open.

Imperative API

Besides controlling the selected date, there is a navigation through months, years, decades that react-datetime handles for us. We can interfere in it, stopping view transtions by using the prop onBeforeNavigate, but we can also navigate to a specific view and date by using some imperative methods.

To do so, we need to create our component with a ref prop amd use the reference.

// This would be the code to render the picker
<DateTime ref="datetime" />

// ... once rendered we can use the imperative API
// let's show the years view
this.refs.datetime.navigate('years')

Available methods are:

  • navigate( viewMode ): Set the view currently shown by the calendar. View modes shipped with react-datetime are years, months, days and time, but you can alse navigate to custom modes that can be defined by using the renderView prop.
  • setViewDate( date ): Set the date that is currently shown in the calendar. This is independent from the selected date and it's the one used to navigate through months or days in the calendar. It accepts a string in the format of the current locale, a Date or a Moment object as parameter.

i18n

Different language and date formats are supported by react-datetime. React uses Moment.js to format the dates, and the easiest way of changing the language of the calendar is changing the Moment.js locale.

Don't forget to import your locale file from the moment's moment/locale folder.

import moment from 'moment';
import 'moment/locale/fr';
// Now react-datetime will be in french

If there are multiple locales loaded, you can use the prop locale to define what language shall be used by the instance.

<Datetime locale="fr-ca" />
<Datetime locale="de" />

Here you can see the i18n example working.

Customize the Input Appearance

It is possible to customize the way that the input is displayed. The simplest is to supply inputProps which will get directly assigned to the <input /> element within the component. We can tweak the inputs this way:

let inputProps = {
    placeholder: 'N/A',
    disabled: true,
    onMouseLeave: () => alert('You went to the input but it was disabled')
};

<Datetime inputProps={ inputProps } />

See the customized input working

Alternatively, if you need to render different content than an <input /> element, you may supply a renderInput function which is called instead.

class MyDTPicker extends React.Component {
    render(){
        return <Datetime renderInput={ this.renderInput } />;
    }
    renderInput( props, openCalendar, closeCalendar ){
        function clear(){
            props.onChange({target: {value: ''}});
        }
        return (
            <div>
                <input {...props} />
                <button onClick={openCalendar}>open calendar</button>
                <button onClick={closeCalendar}>close calendar</button>
                <button onClick={clear}>clear</button>
            </div>
        );
    }
}

See this example working

Or maybe you just want to shown the calendar and don't need an input at all. In that case input={ false } will make the trick:

    <Datetime input={ false } />;

See react-datetime calendar working without an input

Customize the Datepicker Appearance

It is possible to customize the way that the datepicker display the days, months and years in the calendar. To adapt the calendar for every need it is possible to use the props renderDay(props, currentDate, selectedDate), renderMonth(props, month, year, selectedDate) and renderYear(props, year, selectedDate) to customize the output of each rendering method.

class MyDTPicker extends React.Component {
  render() {
    return (
      <Datetime
        renderDay={this.renderDay}
        renderMonth={this.renderMonth}
        renderYear={this.renderYear}
      />
    );
  }
  renderDay(props, currentDate, selectedDate) {
    // Adds 0 to the days in the days view
    return <td {...props}>{"0" + currentDate.date()}</td>;
  }
  renderMonth(props, month, year, selectedDate) {
    // Display the month index in the months view
    return <td {...props}>{month}</td>;
  }
  renderYear(props, year, selectedDate) {
    // Just display the last 2 digits of the year in the years view
    return <td {...props}>{year % 100}</td>;
  }
}

See the customized calendar here.

It's also possible to override some view in the calendar completelly. Let's say that we want to add a today button in our calendars, when we click it we go to the today view:

class MyDTPicker extends React.Component {
  render() {
    return (
      <Datetime
        ref="datetime"
        renderView={(mode, renderDefault) =>
          this.renderView(mode, renderDefault)
        }
      />
    );
  }

  renderView(mode, renderDefault) {
    // Only for years, months and days view
    if (mode === "time") return renderDefault();

    return (
      <div className="wrapper">
        {renderDefault()}
        <div className="controls">
          <button onClick={() => this.goToToday()}>Today</button>
        </div>
      </div>
    );
  }

  goToToday() {
    // Reset
    this.refs.datetime.setViewDate(new Date());
    this.refs.datetime.navigate("days");
  }
}

See it working

Method Parameters

  • props is the object that the datepicker has calculated for this object. It is convenient to use this object as the props for your custom component, since it knows how to handle the click event and its className attribute is used by the default styles.
  • selectedDate and currentDate are moment objects and can be used to change the output depending on the selected date, or the date for the current day.
  • month and year are the numeric representation of the current month and year to be displayed. Notice that the possible month values range from 0 to 11.

Make it work as a year picker or a time picker

You can filter out what you want the user to be able to pick by using dateFormat and timeFormat, e.g. to create a timepicker, yearpicker etc.

In this example the component is being used as a timepicker and can only be used for selecting a time.

<Datetime dateFormat={false} />

Working example of a timepicker here.

In this example you can only select a year and month.

<Datetime dateFormat="YYYY-MM" timeFormat={false} />

Working example of only selecting year and month here.

Blocking some dates to be selected

It is possible to disable dates in the calendar if the user are not allowed to select them, e.g. dates in the past. This is done using the prop isValidDate, which admits a function in the form function(currentDate, selectedDate) where both arguments are moment objects. The function shall return true for selectable dates, and false for disabled ones.

In the example below are all dates before today disabled.

import moment from 'moment';
var yesterday = moment().subtract( 1, 'day' );
var valid = function( current ){
    return current.isAfter( yesterday );
};
<Datetime isValidDate={ valid } />

Working example of disabled days here.

It's also possible to disable the weekends, as shown in the example below.

var valid = function( current ){
    return current.day() !== 0 && current.day() !== 6;
};
<Datetime isValidDate={ valid } />

Working example of disabled weekends here.

Usage with TypeScript

This project includes typings for TypeScript versions 1.8 and 2.0. Additional typings are not required.

Typings for 1.8 are found in react-datetime.d.ts and typings for 2.0 are found in typings/index.d.ts.

import * as Datetime from 'react-datetime';

class MyDTPicker extends React.Component<MyDTPickerProps, MyDTPickerState> {
    render() JSX.Element {
        return <Datetime />;
    }
}

Contributions

react-datetime is made by the community for the community. People like you, interested in contribute, are the key of the project! 🙌🙌🙌

Have a look at our contribute page to know how to get started.

Changelog

MIT Licensed

changelog

Changelog

3.3.1

  • Restores compatibility with React ^16.5.0

3.3.0

  • Adds support for React 19

3.2.0

  • Adds support for React 18

3.1.0

  • Adds support for React 17

3.0.3

  • Localize AM and PM strings
  • Make calendar fluid width
  • Fixes findDOMNode deprecated warning in Strict Mode - Thanks @kkalve
  • Simplification of the base code - Thanks @onlined

3.0.2

  • Fixes typescript typings not being exposed publicly

3.0.1

  • Big refactor, the state is not derived from the props after every update.
  • disableCloseOnClickOutside prop is now closeOnClickOutside (avoid double negations).
  • onBlur and onFocus are renamed to onClose and onOpen since they had nothing to do with the blur event and it was misleading some users. If we want to listen to the input's onBlur and onFocus use inputProps.
  • defaultValue prop is now called initialValue.
  • Updated typescript definitions.
  • Time is not updated anymore on right clicks.
  • Creates renderView prop to customize the whole calendar.
  • Creates updateOnView prop to decide when to update the date.
  • onViewModeChange prop renamed to onNavigate.
  • Creates onBeforeNavigate prop.
  • Creates setViewData and navigate methods.
  • Fixes error clicking on days from the previous or next month in the days view.
  • Fixes month, year and time views for locales that doesn't use gregorian numbers.
  • Adds a playground to make simpler to try out the library by npm run playground.
  • Not depending on gulp to create the build anymore
  • Updated most of the dependencies.

3.0.0

  • This version was published by error and can't be overriden. The first release for v3 branch is 3.0.1

2.16.2

  • Turns moment timezone peer dependency in a runtime error when missing using displayTimezone.

2.16.1

  • Fixes input event overriding

2.16.0

  • The prop disableOnClickOutside has been renamed to disableCloseOnClickOutside
  • The calendar doesn't get closed an open when clicking in the input anymore.
  • Fixes errors not finding dates when customizing day rendering.
  • Event listeners in inputProps now only override default behaviour when returning false.
  • Adds the displayTimeZone prop. Thanks to @martingordon

2.15.0

  • New onNavigateBack and onNavigateForward hooks thanks to @DaanDD and @simeg.
  • Touch improvements by @NicoDos
  • TS and debugging improvements

2.14.0

  • Make viewDate dynamic

2.13.0

  • Use more appropriate cursor for empty space in time picker and in day texts
  • Add viewDate prop that sets a value when opening the calendar when there is no selected date
  • Make disableOnClickOutside work as intended
  • Better touch support for tapping and holding
  • Use static property defaultProps instead of getDefaultProps

2.12.0

  • The renderInput prop now receives closeCalendar function as well

2.11.1

  • The open prop should now work as intended

2.11.0

  • onFocus now receives the browser event
  • Do not open browser menu on right click of arrows in time view
  • Open calendar when onClick is triggered, before it would just react to onFocus
  • Update TypeScript definitions for value and defaultValue to comply with code
  • Fix bug where AM/PM would not sync between component value and input field value
  • Add renderInput prop which let's the consumer of the component render their own HTML input element

2.10.3

  • Update react-onclickoutside dependency
  • Remove isValidDate check before rendering as implementation was causing crashes in some edge cases.

2.10.2

  • Move @types/react back to devDependencies
  • Add demo app.

2.10.1

  • Fix build files.

2.10.0

  • Add isValidDate check before rendering so it doesn't render with an invalid date.

2.9.0

  • Trigger callback method on view mode changes

2.8.11

  • Update TypeScript definitions
  • Replace deprecated React method with non-deprecated method

2.8.10

  • Increase click area of arrows for changing day/month/year
  • Update code according to React 15.5.0
    • Remove usage of React.createClass
    • Use separate module for PropTypes

2.8.9

  • Fixes issue where incorrect current month is shown

2.8.8

  • Fixes issues introduced in v2.8.7 recognizing any calendar view as clickingOutside trigger

2.8.7

  • Update react-onclickoutside dependency. That should fix most of the problems about closeOnSelect.

2.8.6

  • Revert commits related to closeOnSelect that did not fix all issues they were meant to

2.8.5

  • Fix bug where closeOnSelect was not closing when it was set to true
  • Fix bug where component would not immediately re-render when updating either utc or locale prop

2.8.4

  • Fix bug where closeOnSelect=true would cause component to close on state change

2.8.3

  • Fix isValidDate related bug where current month would be invalid
  • Trigger re-render of component when viewMode changes
  • Never append rdtOld class in year view

2.8.2

  • Fix year related bug in tests where year was set to 2016
  • Add a yarnfile so yarn is now possible to use for installing dependencies

2.8.1

  • Fix timeFormat related bug where 'A' was being picked up but not 'a', for setting 12-hour clock.

2.8.0

  • Add typings for TypeScript 2.0. We now support TypeScript typings for versions 1.8 and 2.0.

2.7.5

  • Bumps the version to skip buggy deployment 2.7.4

2.7.4

  • Reverting updating react related dependencies. They were not the issue so they should not be set to the latest version of react.

2.7.3

  • When updating moment to 2.16.0 something broke, hopefully by updating all react prefixed dependencies to 15.4.0 and changing the syntax in the dependency object a bit will resolve this issue.

2.7.2

  • Bug fix: When setting locale and entering month view mode the component would sometimes freeze, depending on the locale. This has now been fixed.

2.7.1

  • Bug fix: onFocus and onBlur were being called in a way causing state to reset. This unwanted behavior is now adjusted.

2.7.0

  • isValidDate now supports months and years.
  • utc prop was added, by setting it to true input time values will be interpreted as UTC (Zulu time).
  • Bug fix: The input value now updates when dateFormat changes.
  • Removed the source-map file because the commit it was introduced in was causing the minified file to be bigger than the non-minified.

2.6.2

  • Update file references in package.json

2.6.1

  • Added a source-map file.
  • Fixed bug with invalid moment object.
  • Decreased npm package size by ~29.3KB.

2.6.0

  • Fixed hover styles for days
  • Added multiple simultaneous datetime component support.
  • className prop now supports string arrays
  • Fixes 12:00am
  • Removed warning for missing element keys.

2.5.0

  • Added pre-commit hook for tests.
  • Added the timeConstraints prop.

2.4.0

  • Added ES linting.
  • Added closeOnTab property.

2.3.3

  • Updated readme.
  • Fixed short months for not English locales.
  • Fixed mixed 12 AM/PM.

2.3.2

  • Time editor now handles the A format to display 12h times.

2.3.0

  • Added typescript definition file.
  • Changed button markup and updated styles.
  • Fixes autoclosing on time change.

2.2.1

  • Controlled datepicker now working for controlled datepickers

2.2.0

  • The picker can be used as a month or year picker just giving a format date without days/months
  • Updates test suite

2.1.0

  • Fixed rdtActive not getting set.
  • Add react-dom as external dependency.
  • Fixed rendering a span directly under the calendar table.
  • Added dev setup
  • Added example

2.0.2

  • Fixed january days go to november problem.

2.0.1

  • Fixed two days can't have the same header name.

2.0.0

  • DOM classes are now prefixed with rdt.
  • A modified version of OnClickOutside is now included in the code to handle react 0.13 and 0.14 versions.
  • Updated dependencies.

1.3.0

  • Added open prop.
  • Added strictParsing prop.
  • Fixed not possible to set value to ''.

1.2.1

  • Removed classlist-polyfill so the component can be used in the server side.

1.1.1

1.1.0

  • Datepicker can have an empty value. If the value in the input is not valid, onChange and onBlur will return input value.
  • onBlur is not triggered anymore if the calendar is not open.

1.0.0-rc.2

  • Added travis CI
  • Fixed not showing timepicker when dateFormat=false.

1.0.0-rc.1

This is the release candidate for this project. Now it is pretty usable and API won't change drastically in a while. If you were using the alpha versions (v0.x) there is a bunch of breaking changes:

  • date prop is now called defaultValue and it is the initial value to use the component uncontrolled.
  • value prop has been added to use it as a controlled component.
  • Removed minDate and maxDate props. Now to define what dates are valid it is possible to use the new isValidDate prop.
  • dateFormat and timeFormat default value is always the locale default format. In case that you don't want the component to show the date/time picker you should set dateFormat/timeFormat to false.

Moreover:

  • Buttons doesn't submit anymore when the Datetime component is in a form.
  • className prop has been added to customize component class.