/en/creating-a-vaadin-flow-server-side-api-for-a-javascript-component/

[mlopezFC]

https://www.flowingcode.com/en/creating-a-vaadin-flow-server-side-api-for-a-javascript-component/

[mlopezFC]

Sami wrote on 2022-10-26 (comment migrated from the previous website):

Hi Martin! This is a good practical explanation. Documentation at https://vaadin.com/docs/latest/create-ui/element-api/client-server-rpc is bit shallow and could link here. How big you see if this is updated to Vaadin 14+? Should webjars still work?

[mlopezFC]

Martín López wrote on 2022-10-26 (comment migrated from the previous website):

Hi Sami!
Thanks for your feedback. This sample project is old, I did a short test updating it to the latest Vaadin 14 version and it is not working for some reason, it seems to be related to webjars. When this article was written npm support was still green, maybe by switching from webjars to npm it should work. I’ll try to test it in that way later and let you know.
Regards!

[mlopezFC]

Sergiu wrote on 2022-10-31 (comment migrated from the previous website):

Hi Martin,
I’m having the same issue as Sami with regard to webjars and running on Vaddin 14. Any feedback ?
Thanks

[mlopezFC]

Martín López wrote on 2022-11-01 (comment migrated from the previous website):

Hi!
I pushed a new branch in the repository that is working on Vaadin 14, would you mind to take a look?
The best way would be to use npm imports but I tried and I couldn’t make it work (I couldn’t even find the exact version that we’re using on the tutorial on npmjs). So I thought that given that these are regular JavaScript libraries, and not JavaScript modules, it is just a matter of changing the JavaScript annotation and replace it with UI.getCurrent().getPage().addJavaScript()
Let me know if that is working also for you.
Regards!