iamkun

Thanks, let's get it to revert to the original one

:tada: This PR is included in version 1.11.5 :tada: The release is available on: - [npm package (@latest dist-tag)](https://www.npmjs.com/package/dayjs/v/1.11.5) - [GitHub release](https://github.com/iamkun/dayjs/releases/tag/v1.11.5) Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:

Agreed. Will update this feature later.

Hi, there's nothing right or wrong of returning 2001 or 2020. All dayjs could do is to guess. And new Date('12/03') also returns 2001 So consistent results parsing anything other...

It might be better to keep the same behavior with JS Date object, and resulting in the same result as `new Date('12/03')`

Thanks for this lovely PR. It is handy in some cases. Maybe, it's better to ship this greet API as a separate plugin, not via dayjs core lib.

> > Thanks for this lovely PR. > > It is handy in some cases. > > Maybe, it's better to ship this greet API as a separate plugin, not...

This dependent on [CustomParseFormat ](https://day.js.org/docs/en/plugin/custom-parse-format)plugin to work

dayjs.tz.setDefault only affect dayjs.tz at present

Well, as for now, NO. We can only set default tz in dayjs.tz. Feel free to open a PR if you need this.