zudo-text

検索したい単語を入力

いつでも検索バーを開ける

l-local-tauriapp-build

Build, verify, and install a Tauri app instance locally for testing. Use when: (1) User says 'build app', 'rebuild app', 'install app', 'l-local-tauriapp-build', (2) User wants to test changes in the ...

Local Tauri App Build & Install

Build a Tauri app instance, verify the build is fresh, and install to /Applications.

Arguments

$ARGUMENTS is the app name (e.g. ztoffice). If empty, ask the user which app to build.

Workflow

Step 1: Clean Cargo cache

Cargo may cache stale frontend assets. Always clean the crate first:

cd tauri-app && cargo clean -p zudotext

Step 2: Build

cd tauri-app && pnpm exec cargo tauri build --config tauri.conf.<app-name>.json

Step 3: Verify built JS

Check that dist-renderer/ JS bundles contain expected code and do NOT contain old code. Pick verification patterns based on what changed in this session.

# Verify new code IS present
grep -c "expected_pattern" tauri-app/dist-renderer/assets/index-*.js

# Verify old code is NOT present (all should be 0)
grep -c "removed_pattern" tauri-app/dist-renderer/assets/index-*.js

If stale, run cd tauri-app && pnpm exec vite build --config vite.config.ts then rebuild.

Step 4: Kill, remove old, install fresh

CRITICAL: cp -rf does NOT reliably update macOS .app bundles. Always move old bundle away first.

killall zudotext 2>/dev/null
sleep 1
mv /Applications/<app-name>.app /tmp/<app-name>-old-$$.app 2>/dev/null
cp -R tauri-app/target/release/bundle/macos/<app-name>.app /Applications/<app-name>.app

Step 5: Verify binary timestamp

stat -f "%Sm" /Applications/<app-name>.app/Contents/MacOS/zudotext

Confirm the timestamp is from just now. If stale, the copy failed.

Step 6: Launch

open /Applications/<app-name>.app

Report the timestamp and that the app is launched. This is a launch check only: do not inspect or mutate the currently signed-in account. A running installed app may be the user's personal daily-driver session. Any agent-driven app interaction must follow the root CLAUDE.md account-isolation rules and .agents/skills/l-cu-test/, including explicit authorization to switch to the designated test account.