Integrate JavaScript frameworks with Tauri
integrating-tauri-js-frontendsskillsetup L2★0
Sheshiyer/skill-clusters ↗What it does
Configure JavaScript frameworks for Tauri v2 static output
Best for
When configuring Next.js, Nuxt, SvelteKit, or Vite for static output in Tauri v2
Inputs
- · Framework choice (Next.js, Nuxt, SvelteKit, Vite), tauri.conf.json settings
Outputs
- · Configured framework files, tauri.conf.json, vite.config.ts or next.config.mjs
Requires
- · Tauri CLI
- · Cargo
- · Node.js
- · npm/yarn/pnpm
Preconditions
- · Tauri v2 project initialized
- · Frontend framework installed
- · SSR must be disabled (Tauri serves static files only)
Failure modes
- · SSR enabled when static output required
- · Frontend dist path wrong (../out vs ../dist vs ../build)
- · beforeDevCommand points to wrong port
- · Image optimization not disabled in Next.js (unoptimized: true missing)
- · SvelteKit adapter not set to static
- · Nuxt SSR not disabled
Trust signals
- · Framework-specific configs (next.config.mjs, svelte.config.js, nuxt.config.ts)
- · Port and devUrl synchronization rules
- · Build command vs dev command distinction
- · Image unoptimization guidance for static export