Doesn't work with 23.3.0

[simasch]

When using Fullcalendar with Vaadin 23.3.0 the application no longer starts.
In the browser log I see

(anonymous) @ index.ts:32
vdom.js:3 Uncaught (in promise) Error: Please import the top-level fullcalendar lib before attempting to import a plugin.
    at vdom.js:3:11

[aetasoul]

Can you provide more details?

Java version
Code to reproduce the problem

[simasch]

@aetasoul Please find a reproducible example here: https://github.com/simasch-scratches/datapicker-validation/tree/fullcalendar-issue

Make sure you checkout the branch fullcalendar-issue

[aetasoul]

I'll check it

[stefanuebe]

Might be a problem regarding the time, when the plugins are registered. Not sure why this comes up with 23.3, but it seems to be a known issue. At least stackoverflow provides a lot of Q&A regarding this. Trying to reproduce and test those.

[stefanuebe]

primefaces/primevue#1211

In my minimal sample it helped to add the line before the Calendar import

import '@fullcalendar/core';

Might be necessary to also add

import '@fullcalendar/core/vdom';

but at least for me now it seemed to work. Will add that for now to fix that issue (I hope it does not break anything else :D)

[stefanuebe]

Released with 4.1.4. Please countercheck, if it also works for you

[simasch]

@stefanuebe No doesn't work for me

Please find a reproducible example here: https://github.com/simasch-scratches/datapicker-validation/tree/fullcalendar-issue
Make sure you checkout the branch fullcalendar-issue

[stefanuebe]

Yes, you are right. On the first load I still get the issue, but on subsequent calls it does not occur anymore. That is really strange.

[stefanuebe]

Can you try if it works for you, when you change the imports in the full-calendar.js to

import '@fullcalendar/core/vdom'; 
import '@fullcalendar/core';

[simasch]

@stefanuebe Yes with this imports it works!

[stefanuebe]

Alright, then 4.1.5 is the version to go

[simasch]

Thanks for your very fast support!

[simasch]

I've opened a new issue with the problem added in 4.1.5
#160