Swap momentjs for another date-io compatible library

DevExpress / devextreme-reactive

Business React components for Bootstrap and Material-UI

https://devexpress.github.io/devextreme-reactive/

Other

2.07k stars 381 forks source link

Swap momentjs for another date-io compatible library #3022

Open adamcarr opened 4 years ago

adamcarr commented 4 years ago

[x] I have searched this repository's issues and believe that this is not a duplicate.

I'm using ...

[ ] React Grid
[ ] React Chart
[x] React Scheduler

Description

We are looking to start using React Scheduler and it has a direct dependency on momentjs which we are trying to avoid due to performance and package bloat. Your dependency on momentjs seems to be via date-io which is an abstraction that may allow swapping out to other libraries. Is this something you currently support or are considering supporting in the future?

Environment

devextreme-reactive: 2.7.0
react: 16.13.1
browser: all
bootstrap: none
react-bootstrap: none
material-ui: none

MaximKudriavtsev commented 4 years ago

Hi @adamcarr,

We are using the moment.js library inside our core package for complex calculations. Unfortunately, it's not possible to change this library.

I assigned an enhancement tag to this issue and we will consider it in future planning.

Can I ask you about what scheduler component your team will prefer and why? This information will help us to become better.

adamcarr commented 4 years ago

We are going to use the React Scheduler in @devexpress/dx-react-scheduler. We will likely use many of the plugins already available as well. We are building a meeting booking system across multiple user accounts and this control greatly simplifies the amount of work we need to do. The question about moment.js is around trying to optimize our package payload and up until now we have been able to avoid moment.js.

MaximKudriavtsev commented 4 years ago

Thank you for the clarification.

FedeBev commented 3 years ago

Hi there,

since moment is now kind of deprecated, maybe this issue should be reconsidered. In my opinion Luxon should allow a smooth migration, but obviously only someone with a deep knowledge of the library can say.