What browser are you using / which timezone are you in?

I'm getting the same error in the US (east coast)

chrome in ET

I had the same when selected was moment.toString() value.
Helped replacing by native js Date object 😎

EDIT: no. It didn't help 😞

Same problem in Chrome 62 OSX, NZDT (+1300), the component was initialised with selected (regardless of being an ISOString or a Date) and display="years" and onSelect, width, height.

I believe this is the issue https://github.com/clauderic/react-infinite-calendar/blob/master/src/Years/index.js#L53

and https://github.com/clauderic/react-infinite-calendar/blob/master/src/utils/index.js#L160
If the selected date is out of range for the month, the next month is returned.

Hey we're also having this issue! I see that @mvayngrib committed a fix. Does that solve it.? It hasn't been merged for a release right?

@leron8 I've had a PR open for 8 months. #150
It fixes the issue.

Thanks @meta-meta , how could I use that fix? would I have to fork this repo and build it myself or is the only option to wait for the pull request to be merged?

@leron8 Yes, I believe that's the only thing you can do until it's merged and published. If you want, feel free to use my fork by adding this to your package.json: "react-infinite-calendar": "meta-meta/react-infinite-calendar#built",

great @meta-meta I see that it's the only change you comparing to the original repo right? master...meta-meta:master ... well besides this: d32f20c but it only changes README.md