b928a6edaf
* Add `generate-docs` command to JS tooling
* Stop generating Rust docs, update JS docs generation
* Change target folder for js copy
* Add recursive to copy
* Add in ARCHITECTURE.md copy
* Add in guides copy
* Change architecture output dir, fix guides destination
* Revert back to GitHub.workspace path
* Change cp to rsync to be able to exclude
* Fix source path
* Change to render title better
* Revert "Change to render title better"
This reverts commit 72b78f3901.
* Fix broken links
1.5 KiB
title
| title |
|---|
| Development Cycle |
import Alert from '@theme/Alert' import Command from '@theme/Command'
1. Start Your Devserver
Now that you have everything setup, you should start your application development server provided by your UI framework or bundler (assuming you're using one, of course).
Every framework has its own development tooling. It is outside of the scope of this document to treat them all or keep them up to date.2. Start Tauri Development Window
The first time you run this command, it will take several minutes for the Rust package manager to download and build all the required packages. Since they are cached, subsequent builds will be much faster, as only your code will need rebuilding.
Once Rust has finished building, the webview will open and it should display your web app. You can make changes to your web app, and if your tooling enables it, the webview should update automatically just like a browser. When you make changes to your Rust files, they will be rebuilt automatically and your app will restart.
In your project repository, you SHOULD commit the "src-tauri/Cargo.lock" along with the "src-tauri/Cargo.toml" to git because Cargo uses the lockfile to provide deterministic builds. As a result, it is recommended that all applications check in their Cargo.lock. You SHOULD NOT commit the "src-tauri/target" folder or any of its contents.