Adam Shaw

This has actually been fixed in [v7.0.0-beta.0](https://github.com/fullcalendar/fullcalendar-workspace/releases/tag/v7.0.0-beta.0) Updated repro: https://codepen.io/arshaw/pen/yLmaJdQ?editors=0010

@hisuwh I will take responsibility for this. Not many people are reporting this type-nerfing problem, so maybe it's your specific case only. [Can you post a Stackblitz?](https://fullcalendar.io/reduced-test-cases)

``` FYI, the V1 API still provides the "/basic" URL that can be used privately, but FullCalendar requires the "/full" URL to get the info it needs, which no longer...

``` We used to use fullcalendar to show events from from a private google calendar within an intranet page. Please keep this scenario into account while implementing oauth / writing...

``` Issue 2678 has been merged into this issue. ``` Reported by `adamrshaw` on 2015-02-10 02:10:06

``` note to self: look at Issue 2678 to investigate the demo w/ angular ``` Reported by `adamrshaw` on 2015-02-10 02:10:33

thanks for the link @DanChadwick

After some debugging I've found that https://cdn.jsdelivr.net/npm/@fullcalendar/[email protected]/+esm and https://cdn.jsdelivr.net/npm/@fullcalendar/[email protected]/index.js/+esm (which is called from the daygrid plugin) are not being correctly deduplicated, resulting in two conflicting version of the fullcalendar core...

I tried debugging this further, but got stuck again. Seems that even if I take care of fullcalendar package deduplication, preact duplicates as well. However, I have a working proof...

seems related to https://github.com/fullcalendar/fullcalendar/issues/4784