Typing bug with dateformat

[dmaggiore-sorint]

Describe the bug
When typing a date without zeros and with a 2digit year, when the day is smaller than 13, it invert the day and the month even though the dateFormat is "dd/MM/yyyy"

To Reproduce

1. react-datepicker with dateFormat="dd/MM/yyyy"
2. type a date like '4/8/24" (4 August 2024)

Expected behavior
I expect to see the date 4th of August 2024 in the Datepicker (and also as value) and not 8th of April 2024

[balajis-qb]

In the above example instead of typing 4/8/24, if you type 4/8/2024 it's correctly parsing or if you change the date format to dd/MM/yy it's working.

[dmaggiore-sorint]

Ok it works with "dd/MM/yy" but then it doesn't work if the user tyèes 4/8/2024 thinking about 4th August instead of 8th of April.

We need to keep the dateFormat in the "dd/MM/yyyy" way and make 4/8/24 work aswell

[balajis-qb]

Hi @martijnrusschen, do you have any thoughts on this issue? I feel as the date format mentioned is not insync with the entered date value, this case is an expected. Let me know if this issue need to be fixed.

[dmaggiore-sorint]

any update on this issue?

[RemigiuszDrozd]

@dmaggiore-sorint @balajis-qb #4004

[martijnrusschen]

I investigated this issue and was unable to reproduce it with the current version.

Test results with dateFormat="dd/MM/yyyy":

• Input "4/8/24" → Not parsed (returns null) because 24 is interpreted as year 24 AD, which fails validation
• Input "4/8/2024" → Correctly parsed as August 4, 2024 ✓
• Input "04/08/2024" → Correctly parsed as August 4, 2024 ✓

The day/month values are not swapped when using the full 4-digit year with dd/MM/yyyy format.

The issue with "4/8/24" not working as expected is a limitation of date-fns parsing: when using yyyy (4-digit year format), the input 24 is interpreted literally as year 24 AD rather than 2024. If you need to support 2-digit year input, use dateFormat="dd/MM/yy" instead.

Could you provide:

1. The exact version of react-datepicker you're using
2. A minimal reproducible example (CodeSandbox or similar)
3. Your locale configuration (if any)

If this is still occurring for you, please share these details and we can investigate further.