Because Vitest runs on a native ESM transformation pipeline, all the ESM errors (needing --experimental-vm-modules), pnpm virtual-store tracking issues (needing package hoisting with reporters) we face under Jest should completely vanish, along with the need for custom transform plugins (like @jgoz/jest-esbuild).
Because Vitest runs on a native ESM transformation pipeline, all the ESM errors (needing
--experimental-vm-modules), pnpm virtual-store tracking issues (needing package hoisting with reporters) we face under Jest should completely vanish, along with the need for custom transform plugins (like@jgoz/jest-esbuild).