gravity-ui / date-utils Goto Github PK

there is a difference between moment and dayjs APIs

dayjs().tz('Europe/Moscow').format('z') // 'GMT+3’
moment(Date.now()).tz('Europe/Moscow').zoneAbbr() // 'MSK’

it seems that it could be a good feature to support timezones abbreviations

I think we can extend dayjs functionality by adding some flag: abbreviateTimezone: true/false and overriding .format() method as following:
format('z') returns GMT +3, after that if abbreviateTimezone flag is turned on, we search through the result string and replace GMT +3 with provided abbreviations

date-utils itself could provide some default abbreviations, like GMT +3 = MSK, however it would be great to have an ability to override default abbreviations

My project stack:

• Next 13.4.3
• React 18.2.0

When i try to import @gravity-ui/date-utils in dev everything works fine, but production build breaks with these errors:

support ability to create a duration

dayjs.duration({ months: 12 })

It would be useful to have a utility for working with the date in utc format. Something like the old version of working with a date or an analog in dayjs:

dayjs.utc('2023-12-31'); // '2023-12-31T00:00Z'
dayjs.utc('2023-12-31T00:00Z'); // '2023-12-31T00:00Z'

In luxon it's very handy method Duration.toFormat. It would be great to have such an ability in date-utils.

I selected Europe/Moscow time zone and tried to enter 12.03.2023, but the result was 12.02.2023

I suggest adding parentheses for keywords and adding new keywords instead of a separator, for example now => now(), /d => today(), /w => week(), /M => month(), /y => year(). It will be more readable this way. Also, this syntax will be easier to convert.

Issue in Vite vitejs/vite#14102

Proposal:
Get rid of variable here and add locales map, smth like:

const langs = {
  ru: () => import(‘dayjs/locale/ru.js’),
  …
};

and load locale in settings.loadLocale:

await langs[locale]();