This fixes some long-standing inconsistencies between
dev mode builds and production builds but is a breaking
change. Dev mode uses custom scheme for Vite versions >= 3.0.0
and for older it still behaves in the old way.
* [assets] Improve error message if no `index.html` could be found in the assets
* [assetoptions] Valide options that at least one property has been set
* [assetserver] Move defaultHTML handling for 404 from assethandler to assetserver
* [assetserver] Add support for serving the index.html file when requesting a directory
* [docs] Update changelog
* [assetserver] Add support for HTTP Middlewares
* [dev] Disable frontend DevServer if no Assets has been defined and inform user
* [dev] Consistent WebSocket behaviour in dev and prod mode for assets handler and middleware
In prod mode we can't support WebSockets so make sure the
assets handler and middleware never see WebSockets in dev mode.
* [templates] Migrate to new AssetServer option
* [docs] Add assetserver.Options to the reference
* Add WindowExecJS
* [devserver] Embed the base frontend into the DevServer struct
* Update docs
Co-authored-by: stffabi <stffabi@users.noreply.github.com>
* [dev] Pass skip bindings to the building process
* [dev] Do not generate bindings in the dev app itself
This is done outside during `wails dev` bootstrapping and
fast regeneration seems to sometime cause locking problems
on Windows.