Does not work. FC 2.3.3 , Vaadin 14.3.4 , SpringBoot 2.2.9. Error: Uncaugh

Directory FullCalendar for Flow
1

Does not work. FC 2.3.3 , Vaadin 14.3.4 , SpringBoot 2.2.9.
Error: Uncaught TypeError: $0.setOption is not a function

Step build-frontend added in Maven. components found in node_modules dir. @EnableVaadin({“org.vaadin.stefan”, “…”}) added too :(

2

Hi, I will try to have a look into this as soon as possible.

3

Hi,

I’ve just tried to reconstruct the problem, but could not. What have I done:

  • downloaded the latest V14 starter (14.3.5, but the patch version shouldn’t be the source of the issue)

  • changed the Spring Boot version to yours

  • added the full calendar dependency

  • added the full calendar to the hello view (plus adding a simple entry)

  • run mvn install on the project

  • run the application via IntelliJ as a Spring Boot Application

  • calendar was shown and fully functional

  • extended the test by adding the annotation @EnableVaadin({“com.example.application”,“org.vaadin.stefan”}), where com.example.application is my current package plus the addon package. > worked

  • run as mvn spring-boot:run > also worked

Can you give me additional details regarding your project? I know, simple question, but had you run mvn (clean) install after adding the full calendar dependency and the full calendar to a class? Also, have you checked, if the full calendar is present in the node modules (looks a bit to me like the frontend dependencies haven’t been resolved correctly).

Best regards
Stefan

4

I just had the same issue with Vaadin 19.0.6, spring boot 2.4.0. It looks it is related to pnpm. I delete all pnpm cache and everything from node_modules and the issue gone.

5

Same problem with 14.6.3, spring boot 2.4.5

Can u share configuration for npm, vaadin and spring boot that it works?

Thanks!

6

It should work out of the box without any further custom config needed then the mentioned one. If you have issues, please open a github issue in my repo with some example code, that allows reproducing the issue.

Best

7

You are right. It was error in configuration of project. Thanks for your response. Componenent works as expected for now. I will check also if new version 3.0.0 is ok