Bernhard P.

One of the problems of offset is the handling of seconds (see issue #1905).

After more tests and investigation here my current interpretation of the original problem of this issue: The code from @irgipaulius compares `dayjs'12/31/2000').utc(true).format(f)` with `moment.utc('12/31/2000').format(f)` and gets different results for the...

I didn't try the code in Chrome, but only on my node.js system. At least in your code above there is a typo in the second line: >import advancedFormat from...

So I will have to test it on Chrome - will be back soon 😄

Tested the following code in chrome (v102.0) and Firefox (v101.0) and got this result:  ``` dayjs issue 1891 dayjs issue 1891 waiting... dayjs.extend(window.dayjs_plugin_advancedFormat) const endDate = '2022-12-31' const formattedDate...

HM, perhaps a type definition thing. Do you have a small demo e.g. in CodeSandbox or something like this?

Perhaps @Kashish-Chaudhary could create a demo of the problem in a [sandbox react playground](https://codesandbox.io/s/rl74rn6q7q)? I tested it with plain typescript (in my repo [dayjs-typescript-demo](https://github.com/BePo65/dayjs-typescript-demo) calling `npm run start:issue1891`) and got...

Yeah, when we "got rid of all the old issues" (e..g. with the `Close Stale Issues` github action), proper moderation will be required for the issues. Today only few issues...

Tested it with the following code in chrome and Firefox on WIndows 10 with dayjs 1.11.3 and the result for 'isValid' was 'true': ``` Parse strict '2017 September 5'  isValid...

As you see, the parsed date is valid (`parsedDate01.isValid()`); the rest is just to see what was parsed (it is a web page 😄 )