- Home
- Skills
- Dchuk
- Claude Code Tauri Skills
- Tauri Binary Size
tauri-binary-size_skill
12
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill dchuk/claude-code-tauri-skills --skill tauri-binary-size- SKILL.md6.7 KB
Overview
This skill guides you through practical techniques to minimize Tauri v2 desktop binary sizes for production releases. It focuses on Cargo profile settings, Tauri build options, and complementary frontend steps to deliver small, efficient application bundles. You’ll get concrete configuration examples and trade-offs so you can balance size, build time, and runtime behavior.
How this skill works
The skill inspects and recommends Rust/Cargo release profile settings (codegen-units, lto, opt-level, panic, strip) and Tauri build options (removeUnusedCommands, feature flags) that reduce included code and debug data. It also highlights frontend optimizations and provides build commands and checks to verify final bundle sizes. Advice includes nightly-only flags and fallbacks when aggressive options cause build issues.
When to use it
- Preparing a production release where installer/binary size matters
- Targeting low-bandwidth distribution or constrained storage devices
- Reducing startup memory and disk footprint for embedded or corporate deployments
- Auditing and trimming unused Tauri command handlers and features
- When you need a repeatable, CI-friendly build configuration for small artifacts
Best practices
- Set profile.release.codegen-units = 1 and enable LTO for whole-program optimization, or use thin LTO if memory is limited
- Use opt-level = "s" or "z" to optimize for size; prefer "s" unless extreme size reduction is required
- Set panic = "abort" and strip = true to remove unwinding and symbol data from release binaries
- Enable tauri.conf.json build.removeUnusedCommands and only include required Tauri features in Cargo.toml
- Audit Rust and frontend dependencies regularly (cargo tree, npm audit) and run size checks after each release
Example use cases
- A cross-platform desktop app shipped to users with limited download bandwidth where reducing installer MBs improves adoption
- A corporate internal tool that must stay under a size threshold for distribution systems
- An embedded kiosk app where disk space and memory are constrained and startup speed benefits from smaller binaries
- CI pipeline that builds release artifacts with deterministic small sizes using the recommended Cargo.toml profile
FAQ
LTO can increase memory use and link time; if builds fail, try lto = "thin" or ensure your build machine has more memory. Test in CI before rolling out.
Does panic = "abort" affect error handling?
Yes. It disables panic unwinding, which reduces size but removes stack-unwinding behavior. Use it when you don’t rely on unwinding for cleanup or error recovery.