* refactor(cli): optimize the template that generates the base template
* refactor: optimize the default vanilla template
* feat(cli): add script to default vanilla template
* refactor(cli): refactor default svelte template and add script
* fix: remove manually added assetdir fields
Manually specified values are removed as the application will automatically infer from embed.FS.
* fix: remove drag attribute within page
* Update v2/cmd/wails/internal/commands/initialise/templates/templates/svelte/frontend/README.md
Co-authored-by: Lea Anthony <lea.anthony@gmail.com>
* [v2] Add support for post build hooks
Currently only supports build-level hooks
* [v2] Improve build assets handling and use single source for manifest generation
The manifest asset files are now a go template and data will be
resolved before they are included into the build output.
Breaking Change: Windows manifest file must be named
“wails.exe.manifest” and doesn’t depend on the project name
anymore.
* [v2, windows] NSIS installer generation
* [linux] Move SetTitle and startDrag to main thread
* [linux] Move SetPosition, Center, Fullscreen and UnFullscreen to main thread
* Fix runtime Window Get/Set Position signatures
* Fix vanilla template keyboard handling
This is interesting if someone uses an asset FS which is not an embed.FS,
but still has some special handling to include loading data from disk in
dev mode. E.g. one might conditionally use an embed.FS or os.DirFS
depending on the build mode.
AssetDir is now inferred from the assets, if the assets is an
embed.FS, by taking the relativ path to the index.html joined with
the project root.
The assetDir flag still exists and can be used if the inferring doesn't
work, because the provided embed.FS wasn't defined in the main
package.
The io/ioutil package has been deprecated as of Go 1.16, see
https://golang.org/doc/go1.16#ioutil. This commit replaces the existing
io/ioutil functions with their new definitions in io and os packages.
Signed-off-by: Eng Zer Jun <engzerjun@gmail.com>
Running `npm install` will now run on the top level of a generated project and additionally the "frontend" workspace (we can add plugins for wails like this, auto update, package, sign, etc, etc)
Other commands that use workspaces (including pre/post hooks mostly) and might be helpful to Wails are `docs`, `install`, `rebuild`, `publish`, `pkg`, `pack`, `ci`
For example, during wails build, you could ask for data from the frontend/package.json to get version, title, etc with.
`npm pkg get name version --workspace=frontend`
Signed-off-by: Snider <snider@lt.hn>
