c.v.flow.component.internal.UIInternals : The component class com.vaadin.flow.component.tabs.TabSheet includes '@vaadin/tabsheet/src/vaadin-tabsheet.js' but this file was not included when creating the production bundle. The component will not work properly. Check that you have a reference to the component and that you are not using it only through reflection. If needed add a @Uses(TabSheet.class) where it is used.
Why does this happen in production mode with components DatePicker, Combobox and TabSheet?
If I had to guess, before the add-on, it was working “on accident” on account of the default bundle. Once the add-on was added, it couldn’t use the default bundle any longer, and scanned accessible packages for used components, and the scan couldn’t find the missing components (as it wouldn’t have done previously, if the scan had run)
I hadn’t been using this configuration until now, and everything was working fine. However, when I encountered this specific issue, adding this configuration fixed the problem.
May I ask you to rerun the maven build with -X flag and optimizeBundle=true and post the output, so that we can try to figure out why the optimized bundle is not working?
If you prefer, you can also create an issue on the Flow GitHub repository , also linking this forum thread.
We use cookies to serve our customers and website visitors in the best possible way. Cookies are used for the proper functioning of the website and for improving the user experience, monitoring visitor traffic and marketing purposes. By continuing to browse the site, you agree to our use of cookies. You can read more about cookies here.
We use cookies to serve our customers and website visitors in the best possible way. Cookies are used for the proper functioning of the website and for improving the user experience, monitoring visitor traffic and marketing purposes. By continuing to browse the site, you agree to our use of cookies. You can read more about cookies here.