rip out tauri bundle (v2), swc -> esbuild, blacksmith -> warpbuild, FAST CI 🚀 (#5328)
- inline mac, windows, linux bundling in the cli - remove tauri bundle from our dep tree - trim down the rpm crate for fewer dependencies in tree - migrate from blacksmith to warpbuild - move off swc and instead use esbuild via tool - use dev drives in windows CI - use fork of nix action for faster caching - test bundling in CI - fix asset handling in linux - add default APPDATA location for webview2 installs for dioxus apps on windows
This commit is contained in:
1 parent
be7296f4f0
commit
b2d01e6779
83 files changed
+7756
-5403
No files matched your search
@@ -131,9 +131,16 @@ impl Config {
|
||||
self
|
||||
}
|
||||
|
||||
/// set the directory where data will be stored in release mode.
|
||||
/// Set the directory where WebView2 stores its user data (cookies, cache, IndexedDB, etc.).
|
||||
///
|
||||
/// > Note: This **must** be set when bundling on Windows.
|
||||
/// If not set, Dioxus automatically chooses a sensible default:
|
||||
/// - **Windows:** `%LOCALAPPDATA%/<exe_name>` — this avoids the WebView2 default of
|
||||
/// placing data next to the executable, which fails in read-only locations like
|
||||
/// `Program Files` or on certain drive types (e.g. ReFS dev drives).
|
||||
/// - **macOS/Linux:** managed by WebKit automatically.
|
||||
///
|
||||
/// You typically only need this if you want multiple apps to share a WebView2 profile
|
||||
/// or need the data in a specific location for compliance/IT policy reasons.
|
||||
pub fn with_data_directory(mut self, path: impl Into<PathBuf>) -> Self {
|
||||
self.data_dir = Some(path.into());
|
||||
self
|
||||
|
||||
Reference in new issue
Block a user