tauri-migration_skill

Overview

This skill assists developers migrating Tauri applications to v2 stable from either v1 or v2 beta. It focuses on breaking changes, configuration and Cargo updates, API and plugin migrations, and platform-specific adjustments to get apps building and behaving correctly. You get a practical checklist, automated migration guidance, and targeted fixes for common pitfalls.

How this skill works

The skill explains what the Tauri CLI migration does and what requires manual review. It inspects configuration changes (top-level keys, bundle reorganization, new required fields), Rust and JS API differences, plugin replacements, capabilities files, and environment variable renames. It also highlights platform-specific items like Windows origin URL and mobile development tweaks.

When to use it

• Migrating a Tauri v1.x project to v2 stable
• Upgrading a v2 beta project to v2 stable
• Preparing production builds after CLI migration
• Adapting Rust and JavaScript code to the v2 plugin system
• Fixing runtime issues after automated migration

Best practices

• Run npm install @tauri-apps/cli@latest then npm run tauri migrate, but always manually review changes
• Add mainBinaryName to config that exactly matches productName
• Replace the v1 allowlist with capabilities JSON files under src-tauri/capabilities/
• Install and register required plugins in both Cargo.toml and your Rust builder code
• Test Windows IndexedDB/cookie behavior and set useHttpsScheme if you need to preserve state

Example use cases

• Automate initial config and capability generation, then manually map renamed keys and fields
• Replace tauri::api usage with official v2 plugins and update imports in JS and Rust
• Resolve broken FS calls by switching to @tauri-apps/plugin-fs and updating function names (createDir -> mkdir, etc.)
• Migrate menu and tray code to new builders and event handlers in Rust
• Prepare a cross-platform build including mobile by updating Cargo.toml and adding mobile entry points