-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vaadin 23.2 Vite not working with Liferay portlets #240
Comments
For Vite build tool we can generate a basic stats.json in Flow, so Portlet wouldn't throw an error. |
Seems there is another issue, that For now there is a workaround - but it is not a pretty one as portlets will include static files as well:
|
The problem with |
For multimodule projects, there's a workaround, but it requires a bit of configuration. An example can be found in the |
Update maven war plugin configuration to pack static files in the expected position. Webpack is used because currently there's an issue running Vite with Portlet (see vaadin/portlet#240).
Currently, Vaadin portlets only work with Webpack. References vaadin/portlet#240
Update maven configuration to support Vaadin 23.2+ Enables Webpack, because of an issue with Vite (vaadin/portlet#240). References vaadin/portlet#243
Update maven war plugin configuration to pack static files in the expected position. Webpack is used because currently there's an issue running Vite with Portlet (see vaadin/portlet#240).
Update maven configuration to support Vaadin 23.2+ Enables Webpack, because of an issue with Vite (vaadin/portlet#240). References vaadin/portlet#243
Update maven war plugin configuration to pack static files in the expected position. Webpack is used because currently there's an issue running Vite with Portlet (see vaadin/portlet#240).
Vaadin 23.2 using default settings (using Vite) builds but when portlets are deployed on Liferay fails with missing stats.json.
Versions:
Server logs:
The text was updated successfully, but these errors were encountered: