-
Notifications
You must be signed in to change notification settings - Fork 4
Tryout Tauri to build desktop versions #286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for freedevtool ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR adds Tauri integration to enable building desktop versions of FreeDevTool.App. The changes introduce necessary Tauri configuration files, Rust source code for the desktop wrapper, application icons, and Vite configuration adjustments to support Tauri's development workflow.
Key changes:
- Tauri configuration and Rust application wrapper setup
- Desktop and mobile application icons in multiple formats
- Vite configuration updates for Tauri compatibility (clearScreen, strictPort)
Reviewed changes
Copilot reviewed 14 out of 66 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| vite.config.ts | Added Tauri-compatible Vite settings (clearScreen: false, strictPort: true) |
| src-tauri/tauri.conf.json | Main Tauri configuration defining app metadata, build settings, and window properties |
| src-tauri/src/main.rs | Rust entry point that delegates to library code |
| src-tauri/src/lib.rs | Core Tauri application setup with debug logging |
| src-tauri/Cargo.toml | Rust package manifest with Tauri dependencies |
| src-tauri/build.rs | Build script for Tauri code generation |
| src-tauri/capabilities/default.json | Permission configuration for Tauri capabilities |
| src-tauri/icons/* | Application icons for various platforms (iOS, Android, desktop) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 14 out of 67 changed files in this pull request and generated 3 comments.
| } | ||
| ], | ||
| "security": { | ||
| "csp": null |
Copilot
AI
Dec 22, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Content Security Policy is set to null, which disables CSP protection entirely. This poses a security risk as it allows any content to be loaded. Consider defining a restrictive CSP that allows only necessary sources, especially since this is an offline-first application.
| serde = { version = "1.0", features = ["derive"] } | ||
| log = "0.4" | ||
| tauri = { version = "2.9.5", features = [] } | ||
| tauri-plugin-log = "2" |
Copilot
AI
Dec 22, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tauri-plugin-log dependency is specified without a version constraint. This could lead to compatibility issues or breaking changes when dependencies are updated. Specify an explicit version (e.g., "2.0.0") to ensure reproducible builds.
| tauri-plugin-log = "2" | |
| tauri-plugin-log = "2.0.0" |
| if cfg!(debug_assertions) { | ||
| app.handle().plugin( | ||
| tauri_plugin_log::Builder::default() | ||
| .level(log::LevelFilter::Info) | ||
| .build(), | ||
| )?; | ||
| } |
Copilot
AI
Dec 22, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The logging plugin is only enabled in debug mode but there's no documentation explaining this behavior. Consider adding a comment to explain why logging is debug-only and what happens in production builds.
No description provided.