Dylan Ferris

I tested in this example project and don't get that warning with yarn v1.22.21: https://github.com/fullcalendar/fullcalendar-examples/tree/main/moment-timezone Please post a [runnable, stripped-down demonstration](http://fullcalendar.io/wiki/Reduced-Test-Cases/) or steps to reproduce the bug.

I don't believe `@fullcalendar` plugins are compatible with the bundled version, although it's not clear in the docs so I'll reopen. It should work with `@fullcalendar/core` as in this example:...

I'm not sure that would work in general since events are rendered after the day cells. You could do it manually by adding the classes after the event rendering (based...

The `resources` setting is not a view-specific option currently. You could supply the resources as a function to change them based on the view as here: https://github.com/fullcalendar/fullcalendar/issues/4934#issuecomment-500493144

Thanks confirmed. Seems related to https://github.com/fullcalendar/fullcalendar/issues/7666

I can see the flickering but I'm not sure it's actually a bug in the calendar. I believe the issue is from using `useState` to reintialize the calendar when the...

Thanks, confirmed. Also get the same without React: https://codepen.io/acerix/pen/yLadWXQ?editors=001

I'm not sure of the issue with how it's displayed, how are you wanting it to look in this case? You could switch to the `timeGridDay` when there are no...

Thanks for the details, it does seem like a bug in that example with the inconsistent borders. Since it looks ok without `datesAboveResources`, you could turn that off when there...

Sorry for the delay in responding to your issue, I have just began triaging on this repo. Please see this post about the state of the repo (https://github.com/fullcalendar/fullcalendar-react/issues/66) for more...