When user timezone is Europe/Lisbon, the tempo's range function throws an "Invalid offset" exception.

[sashamilenkovic]

Reproduction can be seen on the @formkit/tempo docs itself by editing the range example and passing the token years. Issue occurs when timezone is Europe/Lisbon though I'm sure there are others.

[kswedberg]

I just started seeing this when I updated FormKit to 1.5.7 and FormKit Pro to 0.126.11, but I'm in America/Detroit timezone.

Can you recommend a version to revert to until this issue is fixed?

[kswedberg]

To be clear, the error I'm seeing is Invalid offset: -05:32.18333333333334

[kswedberg]

So sorry for spamming the comments here! I should mentioned that the problem occurs with the following schema:

[
 {
    $formkit: 'datepicker',
    name: 'date',
    format: 'DD-MMM-YYYY',
    valueFormat: 'YYYY-MM-DD',
    validation: 'required',
    overlay: true,
  },
]

[justin-schroeder]

Wow, this is obscure. It has to do with the really old dates in certain timezones. When we use the YYYY token with range() token, we scan -120 years and + 50 or so. It turns out that some timezones return very odd results for dates in 1904 specifically. For example in America/Detroit if you run:

new Date('1904-06-06T00:00:00')
// 1904-06-06T05:32:11.000Z

where is that 32:11 coming from? Well it turns out that January 1st 1905 the clocks moved from LMT to CST — so the resulting time is actually accurate. Our internal methods were not expecting a timezone offset to have seconds in them. Since these 11 seconds are not particularly important we will round them going forward.

[justin-schroeder]

@kswedberg this should be fixed in 0.1.2

[kswedberg]

Thanks so much, @justin-schroeder ! Works like a charm now 😃