Bernhard P.

Just to support the arguments given so far: * for this use case (4 digit year below 100) the behavior of dayjs is different from what moment does (parses year...

Good question - depends on the review capacity of @iamkun

The year 2020 has a week numbered '53' (is a consequence of what weekday a year starts with) - details can be found e.g. in [rosecalendars](https://www.rosecalendars.co.uk/news/the-reason-and-logic-behind-this-phenomenon/).

Good idea. The default (internal) format is json. Can I motivate you to create a json-to-md-formatter, e.g. by using the [tablemark](https://www.npmjs.com/package/tablemark) package ?-)

Give me a few days for a deeper look - especially I am thinking about the configuration for the tablemark package.

oh, it does (forget about looking at the **internal** variable $d :-) ``` console.log(oldDateDayjsTest1.format()) // => '2022-10-29T12:00:00+02:00' console.log(oldDateDayjsTest1.toISOString()) // => '2022-10-29T10:00:00.000Z' console.log(oldDateDayjsTest1.toString()) // => 'Sat, 29 Oct 2022 10:00:00 GMT'...

Just a more extensive explanation: + dayjs.tz("2021/12/25", "YYYY/MM/DD", "America/Phoenix") parses the given string for the given timezone. So `date.format()` will show '2021-12-25T00:00:00-07:00' - as expected. + looking at the **internal**...

The plugin is not yet implemented. Feel free to create a pr for that 😃

**Urgent question about the base branch for dayjs2.0** @sxzz I am currently working on implementing the more complicated plugins for dayjs 2.0 ('utc', 'CustomParseFormat'); my base for this code is...

@StefanoMagrassi thanks for the hint - indeed I missed that point (and fixed it now).