Closed enver-haase closed 2 days ago
vite.config.ts
is not ignored.
The linked issues are related to problems with custom port and protocol for Vite server, that are handled at runtime by Flow ViteHandler
class when starting Vite.
Is the application perhaps using the default bundle?
You can try to set forceProductionBuild
to true in the POM file and check if the custom Vite configuration is applied.
EDIT: I am assuming the issue happens during production build
So we tried it out and it works. So the issue can be closed.
Thanks. That was the info we needed.
Description of the bug
in the
vite.config.js
Both https://github.com/postcss/autoprefixer and https://github.com/postcss/postcss-load-config did not work. It seems that vite.config.js is ignored entirely(?) by Vaadin?
See also, for example, https://github.com/vaadin/flow/issues/19069 and https://github.com/vaadin/flow/issues/14773 which are also complaining about Vite configuration items being ignored.
Minimal reproducible example
Try above code snippet for the vite configuration.
Expected behavior
Actual behavior
Versions: