You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Prevent application startup if webpack config file is present while running with Vite #14417
As of V23.2, the default frontend build tool is changed to Vite (and webpack is only available behind a feature flag).
Applications migrating from earlier versions normally have the legacy webpack.config.js, should be notified about the fact that any webpack configuration will not be picked by Vite.
Describe the solution you'd like
To prevent confusion and misconfiguration, a runtime exception should prevent application startup if webpack.config.js exists in the project and it contents are different from the default that is created by Vaadin. The exception message should clearly ask the user to either:
Migrate any custom webpack configs to Vite alternatives and remove the webpack.config.js to be able to run the application with Vite.
Reactivate the webpack with its associated feature flag to continue running the application with webpack.
If the webpack.config.js exists but the contents were the autogenerated content by Vaadin, only WARN the user about its existence and don't prevent the application startup.
Activity
feat: throw exception if webpack config file exist and running with Vite
feat!: throw exception if webpack config file exist and running with …
vaadin-bot commentedon Sep 7, 2022
This ticket/PR has been released with Vaadin 23.2.0.