[docs] When can you parse without the `CustomParseFormat` plugin?

[rakleed]

Describe the bug
String + Format (https://github.com/dayjs/dayjs-website/blob/master/docs/parse/string-format.md) does not specify when the CustomParseFormat plugin can be omitted. The second line "This requires the CustomParseFormat plugin to work" makes it seem like you should always use the plugin.

Expected behavior
List all cases where you can parse without the CustomParseFormat plugin. ChatGPT reports these cases:

YYYY-MM-DD
YYYY-MM-DDTHH:mm:ssZ
YYYY-MM-DDTHH:mm:ss.SSSZ
YYYY-MM-DDTHH:mm
YYYY-MM-DDTHH
YYYY-MM
YYYY
MM-DD
HH:mm:ss
HH:mm

Information

• Day.js version: 1.11.13
• OS: N/A
• Browser: N/A
• Time zone: N/A

[vladrusu]

I agree.
My expectation is that dayJS should parse combination of locale-insensitive parameters like MM, DD, YYYY by default.
So, should be able to parse this by default:
dayjs("18/10/2024", "DD/MM/YYYY")
This should be core stuff.

Only for stuff like MMMM like dayjs("2018 Enero 15", "YYYY MMMM DD", "es") to require a plugin.