debugging-tauri-apps

Configures debugging workflows for Tauri v2 applications across VS Code, RustRover, and Neovim.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/dt418/better-shot-x --skill debugging-tauri-apps-dt418
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-tauri-apps
Source: https://github.com/dt418/better-shot-x/tree/main/.agents/skills/debugging-tauri-apps
Command: npx skills add https://github.com/dt418/better-shot-x --skill debugging-tauri-apps-dt418

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging Tauri v2 applications is difficult because the app spans a Rust backend and a WebView frontend, and standard IDE debuggers bypass the Tauri CLI, breaking dev server startup and breakpoint attachment. This Skill provides working configurations and workflows for each major editor. ## Core Features & Use Cases - IDE Debug Configurations: Ready-to-use launch.json, tasks.json, and Run Configuration setups for VS Code (LLDB/cppvsdbg), RustRover/IntelliJ, and Neovim (nvim-dap + codelldb). - WebView and Console Debugging: Instructions for opening WebView DevTools programmatically, enabling Rust backtraces, and using conditional compilation (cfg(dev), debug_assertions) to separate debug from production code. - CrabNebula DevTools Integration: Setup of tauri-plugin-devtools for real-time log inspection, IPC command timing, and event analysis. - Use Case: Your breakpoints in Rust code are never hit when running tauri dev from VS Code. This Skill explains that you must build with --no-default-features and configure a preLaunchTask to start the frontend dev server before the debugger attaches. ## Quick Start Ask the assistant to set up a VS Code debug configuration for your Tauri v2 app so breakpoints in Rust code are hit during development.

Frequently Asked Questions about debugging-tauri-apps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a Tauri app in VS Code?

Install the vscode-lldb extension and create a launch.json configuration that builds via cargo with --no-default-features. Add a preLaunchTask in tasks.json to start the frontend dev server, then press F5 to attach the debugger to Rust breakpoints.

Why are my breakpoints not hit when debugging Tauri?

Breakpoints are missed when the app is built without the --no-default-features flag, which makes Tauri load bundled assets instead of the dev server. Also ensure the frontend dev server is running before the Tauri app starts.

How do I open WebView DevTools in a Tauri app?

Right-click and select Inspect Element, or press Ctrl+Shift+i on Linux/Windows and Cmd+Option+i on macOS. You can also call window.open_devtools() programmatically inside a debug_assertions block during setup.

Can I debug Tauri apps in Neovim?

Yes, using nvim-dap with the codelldb adapter, plus nvim-dap-ui for the debugger interface. Configure a launch configuration pointing to the compiled binary in target/debug and start the dev server separately via overseer.nvim.

Does enabling devtools in production Tauri builds have risks?

Yes, enabling the devtools feature in production uses private macOS APIs that prevent App Store acceptance. Prefer tauri build --debug for testing instead of permanently enabling the feature flag.

What is CrabNebula DevTools for Tauri?

CrabNebula DevTools is a plugin (tauri-plugin-devtools) that provides real-time instrumentation for Tauri apps, including log inspection, IPC command timing, and event payload analysis through a web-based interface during tauri dev.