window.Vaadin.Flow.tryCatchWrapper is not a function

[aze-kool]

Hi,
We have updated our software from 14.0.0.rc2 to 14.1.17. we are currently running in Compatibility Modus. Unfortunately we are getting the following error. we also tried the version14.2.0.alpha3 and the Error exist in this version as well.

once we go back to version 14.0.0.rc2 error disappears.

can you please have a look at this error.

2client-FCCC15DDC39AFA7323E81DFDEFA160A8.cache.js:184 Uncaught TypeError: window.Vaadin.Flow.tryCatchWrapper is not a function
    at tryCatchWrapper (contextMenuConnector.js:6)
    at Object.init (contextMenuConnector.js:14)
    at HTMLElement.eval (eval at Tt (client-FCCC15DDC39AFA7323E81DFDEFA160A8.cache.js:998), <anonymous>:3:62)
    at Object.eval (eval at Tt (client-FCCC15DDC39AFA7323E81DFDEFA160A8.cache.js:998), <anonymous>:3:120)
    at Tt (client-FCCC15DDC39AFA7323E81DFDEFA160A8.cache.js:998)
    at St (client-FCCC15DDC39AFA7323E81DFDEFA160A8.cache.js:954)
    at Qt (client-FCCC15DDC39AFA7323E81DFDEFA160A8.cache.js:576)
    at wr (client-FCCC15DDC39AFA7323E81DFDEFA

[ZheSun88]

Hi @aze-kool ,

Thanks for using Vaadin.

when you update your project, may i ask you to remove the auto generated package-lock.json package.json and bower-components from your project beforehand? then run the project again.

if this doesn't help you, please, provide us some example projects to reproduce the problem.

BR

[aze-kool]

Hi @ZheSun88
Thanks for a reply,
As i mentioned, we are running our app in compatibility modus. so there are no package-lock.json package.json or bower-components exists.

I think the following image can get you started, As the problem source is clearly seen here.

[ZheSun88]

Hi @aze-kool ,

sorry for misleading you with the *.json files, but if you are running the project in compatibility modules, there should be a folder named bower-components. that probably the one causing the component conflicts.

if that cannot help with your project, take a look about this issue vaadin/flow#7463 .

BR

[aze-kool]

Hi @ZheSun88
Thanks for the Link of @flow#7463 .

As far as i know, there is no need of bower_components folder in Flow-13. As webjars is the way to integregate external component. for custom component we use frontend/src folder.

I think, Vaadin Flow somehow handles it dynamically. I can't find any bower_components under my project directory as well.

https://vaadin.com/docs/v13/flow/web-components/integrating-a-web-component.html

Best Regards

[ZheSun88]

Hi @aze-kool ,

is your issue related to the linked ticket?
if so, you can comment in that bug ticket too.
if not, i would suggest you to provide us a small project which can reproduce the issue. we have some internal projects using Vaadin 14.1.17, but it works okay for us.

[web-padawan]

This should no longer be a problem with Vaadin 14.3 and 14.4 as well as Vaadin 17. Closing.