Commands

These are commands to use inside an actual Tauri app repository. They are not proof that this learn pack has built Tauri; this run did not install packages, clone repos, or execute third-party project builds.

Create And Develop

TaskCommandNotes
Create appnpm create tauri-app@latestRecheck current official create command before use
Run desktop devnpm run tauri devFrontend dev server plus Tauri desktop shell
Run Rust checkscargo test --manifest-path src-tauri/Cargo.tomlUse from repo root when src-tauri/ exists
Run frontend testsnpm testProject-specific; use Vitest or existing runner
Build desktopnpm run tauri buildProduces release bundles for current OS target

Use the package manager already present in the project. Do not switch from npm to pnpm, Yarn, Bun, or Cargo-only scaffolding just because a snippet uses it.

Frontend Quality

npm run lint
npm run typecheck
npm test

If the project has no lint/typecheck/test scripts, add or document the missing quality gate before claiming production readiness.

Rust Quality

cargo fmt --manifest-path src-tauri/Cargo.toml --check
cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets -- -D warnings
cargo test --manifest-path src-tauri/Cargo.toml

Only run these after you verify the app uses Cargo in src-tauri/ and dependencies are already installed or approved.

Desktop Build And Smoke

npm run tauri build

After build:

  1. Record the bundle path.
  2. Install or launch the release artifact, not the dev server.
  3. Check the capability-dependent flows.
  4. Check sidecar startup and shutdown if present.
  5. Check logs and crash behavior.
  6. Record OS, architecture, WebView2/WebKitGTK/WKWebView notes, and signing state.

Mobile Smoke

npm run tauri android init
npm run tauri android build -- --apk
npm run tauri android build -- --aab
npm run tauri ios init
npm run tauri ios build

Treat these as platform-specific commands. Android requires Android Studio, SDK/NDK setup, environment variables, and Rust Android targets. iOS requires macOS, Xcode, iOS Rust targets, and CocoaPods.

Updater Artifacts

Do not enable updater artifacts until signing keys and endpoints are planned.

Checklist before a build can claim updater readiness:

updater plugin registered
public key in tauri config
private signing key supplied through approved secrets path
createUpdaterArtifacts intentionally configured
static JSON or dynamic update endpoint reachable
artifact signatures produced
install and relaunch flow tested
lost-key recovery plan documented

Command Claim Boundaries

EvidenceAllowed claim
npm run tauri dev worksDesktop dev shell runs
cargo test passesRust tests pass
Frontend tests pass with mockIPCRenderer IPC wrapper is tested
npm run tauri build creates artifactRelease artifact produced for this OS
Artifact installed and launchedRelease smoke passed on that OS
Signed artifact verifiedOS signing proof exists
Updater signature and install testedUpdater path passed for that platform
Android emulator/device testedAndroid smoke passed
iOS device/simulator testediOS smoke passed