parseISO parses number '30' when it should error.

[sheki]

Behavior

const { parseISO} = require('date-fns');
console.log(parseISO('30')); // prints '3000-01-01T08:00:00.000Z'

This should error/return invalid date instead of parsing.

Similar code in golang returns an error when parsing '30'.
https://go.dev/play/p/L8_zo40vNNA

[piet-maier]

The documentation states:

Function accepts complete ISO 8601 formats as well as partial implementations.

In other words: This is the expected behavior.

[stanleyk]

Well... Although formally correct, this substantially reduces the usability of such parsing. The likelihood of "30" and such being an intentional representation of "30th century" is virtually zero. It would help a lot, if this behavior were an opt in.