vite-wasm-setup

name	vite-wasm-setup
description	Guide to configuring Vite for Miden WASM applications. Covers the midenVitePlugin() setup, COOP/COEP headers, production deployment headers, TypeScript compatibility, and troubleshooting common Vite + WASM issues. Use when setting up a new Miden frontend, debugging build or runtime errors related to WASM or Vite configuration, or deploying to production.

Vite + WASM Configuration for Miden

Required vite.config.ts

import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";
import { midenVitePlugin } from "@miden-sdk/vite-plugin";

export default defineConfig({
  plugins: [react(), midenVitePlugin()],
});

midenVitePlugin() works with no options for the common case — the default @miden-sdk/miden-sdk / @miden-sdk/react imports ship single-threaded (ST) WASM that loads in any browser context, so the default client runs with no cross-origin isolation. The plugin's crossOriginIsolation option defaults to false for the same reason, and the v0.15.0 example wallet app calls midenVitePlugin() bare. Don't reach for crossOriginIsolation: true unless you have actually opted into the multi-threaded build (see below).

Pass if you import the WASM variant — (or ) and (or ). The MT build uses and / for ~3–5x faster local proving, which the browser only constructs when the page is cross-origin-isolated (COOP + COEP ). On the default ST imports those headers are unnecessary. The 's is the source-of-truth reference for the current setup.