The Plugin Ecosystem

"Most 'how do I do X natively' questions in Tauri have the same answer: there's a plugin for that."

Batteries, Officially Included

The Tauri team maintains a set of official plugins covering the native features apps need most. A non-exhaustive tour: fs (filesystem), dialog (open/save/message dialogs), shell (open URLs, run processes), http (HTTP client from Rust, no CORS), store (persistent key-value JSON), clipboard-manager, notification, os (platform info), global-shortcut, opener, process, and updater. Each is a separate crate plus a JS module, versioned alongside Tauri 2.

The tauri add Shortcut

You can wire a plugin by hand, but tauri add <plugin> does much of it for you: it adds the Rust crate, installs the JS package, and often registers the builder line. You'll still confirm the capability permission (the third surface — next lesson), but the CLI removes most of the boilerplate. For the official plugins, reach for tauri add first.

Official vs Community

Beyond the official set, the awesome-tauri list collects community plugins for everything from SQL to websockets to system info. Official plugins move in lockstep with Tauri releases and are the safest default; community plugins fill gaps but vary in maintenance — check their last update and Tauri-2 compatibility before depending on one. The instinct from the four pillars applies: prefer reusing a maintained plugin over reinventing it, but vet what you depend on.

Code

tauri add does most of the wiring·bash

# Add an official plugin — wires the Rust crate + JS package for you.
npm run tauri add dialog
npm run tauri add fs
npm run tauri add store

# Equivalent manual path (if you prefer): add the crate yourself.
cargo add tauri-plugin-dialog --manifest-path src-tauri/Cargo.toml
npm install @tauri-apps/plugin-dialog

Exercise

Browse the official plugin catalog and pick three plugins your dream app would actually use. For each, write one sentence on what native capability it gives you and why a plugin beats writing it yourself. You're building a map of 'batteries available' so you never hand-roll something the ecosystem already solved.

Hint

Common picks: store (settings persistence), dialog (native file pickers), notification (OS notifications), global-shortcut (hotkeys), updater (auto-updates). The 'why a plugin' answer is usually 'cross-platform edge cases already handled.'