Gathering detailed insights and metrics for react-datetime
Gathering detailed insights and metrics for react-datetime
Gathering detailed insights and metrics for react-datetime
Gathering detailed insights and metrics for react-datetime
rc-datetime-picker
React datetime picker by momentjs
input-moment
React datetime picker powered by momentjs
input-moment-fork
React datetime picker powered by momentjs
material-ui-datetime-range-picker
React Datetime Range Picker Component that Implements Google's Material Design Via Material-UI.
A lightweight but complete datetime picker react component.
npm install react-datetime
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
2,000 Stars
614 Commits
869 Forks
22 Watching
12 Branches
67 Contributors
Updated on 03 Nov 2024
Minified
Minified + Gzipped
JavaScript (94.35%)
TypeScript (2.34%)
CSS (2.28%)
HTML (1.03%)
Cumulative downloads
Total Downloads
Last day
-2.9%
43,922
Compared to previous day
Last week
2.3%
230,157
Compared to previous week
Last month
4.7%
965,226
Compared to previous month
Last year
-7%
11,047,989
Compared to previous year
1
71
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.
Install using npm:
1npm install --save react-datetime
Install using yarn:
1yarn add react-datetime
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.
1// Import the library 2import Datetime from 'react-datetime'; 3 4// return it from your components 5return <Datetime />;
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:
1import "react-datetime/css/react-datetime.css";
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. |
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.
1// This would be the code to render the picker 2<DateTime ref="datetime" /> 3 4// ... once rendered we can use the imperative API 5// let's show the years view 6this.refs.datetime.navigate('years')
Available methods are:
years
, months
, days
and time
, but you can alse navigate to custom modes that can be defined by using the renderView
prop.Date
or a Moment
object as parameter.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.
1import moment from 'moment'; 2import 'moment/locale/fr'; 3// 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.
1<Datetime locale="fr-ca" /> 2<Datetime locale="de" />
Here you can see the i18n example working.
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:
1let inputProps = { 2 placeholder: 'N/A', 3 disabled: true, 4 onMouseLeave: () => alert('You went to the input but it was disabled') 5}; 6 7<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.
1class MyDTPicker extends React.Component { 2 render(){ 3 return <Datetime renderInput={ this.renderInput } />; 4 } 5 renderInput( props, openCalendar, closeCalendar ){ 6 function clear(){ 7 props.onChange({target: {value: ''}}); 8 } 9 return ( 10 <div> 11 <input {...props} /> 12 <button onClick={openCalendar}>open calendar</button> 13 <button onClick={closeCalendar}>close calendar</button> 14 <button onClick={clear}>clear</button> 15 </div> 16 ); 17 } 18}
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:
1 <Datetime input={ false } />;
See react-datetime calendar working without an input
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.
1class MyDTPicker extends React.Component { 2 render() { 3 return ( 4 <Datetime 5 renderDay={this.renderDay} 6 renderMonth={this.renderMonth} 7 renderYear={this.renderYear} 8 /> 9 ); 10 } 11 renderDay(props, currentDate, selectedDate) { 12 // Adds 0 to the days in the days view 13 return <td {...props}>{"0" + currentDate.date()}</td>; 14 } 15 renderMonth(props, month, year, selectedDate) { 16 // Display the month index in the months view 17 return <td {...props}>{month}</td>; 18 } 19 renderYear(props, year, selectedDate) { 20 // Just display the last 2 digits of the year in the years view 21 return <td {...props}>{year % 100}</td>; 22 } 23}
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:
1class MyDTPicker extends React.Component { 2 render() { 3 return ( 4 <Datetime 5 ref="datetime" 6 renderView={(mode, renderDefault) => 7 this.renderView(mode, renderDefault) 8 } 9 /> 10 ); 11 } 12 13 renderView(mode, renderDefault) { 14 // Only for years, months and days view 15 if (mode === "time") return renderDefault(); 16 17 return ( 18 <div className="wrapper"> 19 {renderDefault()} 20 <div className="controls"> 21 <button onClick={() => this.goToToday()}>Today</button> 22 </div> 23 </div> 24 ); 25 } 26 27 goToToday() { 28 // Reset 29 this.refs.datetime.setViewDate(new Date()); 30 this.refs.datetime.navigate("days"); 31 } 32}
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
.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.
1<Datetime dateFormat={false} />
Working example of a timepicker here.
In this example you can only select a year and month.
1<Datetime dateFormat="YYYY-MM" timeFormat={false} />
Working example of only selecting year and month here.
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.
1import moment from 'moment'; 2var yesterday = moment().subtract( 1, 'day' ); 3var valid = function( current ){ 4 return current.isAfter( yesterday ); 5}; 6<Datetime isValidDate={ valid } />
Working example of disabled days here.
It's also possible to disable the weekends, as shown in the example below.
1var valid = function( current ){ 2 return current.day() !== 0 && current.day() !== 6; 3}; 4<Datetime isValidDate={ valid } />
Working example of disabled weekends here.
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
.
1import * as Datetime from 'react-datetime'; 2 3class MyDTPicker extends React.Component<MyDTPickerProps, MyDTPickerState> { 4 render() JSX.Element { 5 return <Datetime />; 6 } 7}
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.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
Found 8/14 approved changesets -- score normalized to 5
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
license file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More