Vite 8.0.0‑beta.14 adds server‑side .wasm?init (WASM SSR) and updates Rolldown to 1.0.0‑rc.4
Vite published v8.0.0‑beta.14 (Feb 12, 2026), which explicitly adds server-side support for importing pre-initialised WebAssembly via the .wasm?init import pattern and upgrades its bundler dependency to Rolldown 1.0.0‑rc.4. (github.com)
Why this matters for full‑stack teams
- Server‑side .wasm?init (WASM SSR): Vite's SSR pipeline can now treat a .wasm?init import as a server-side, pre-initialised WebAssembly module during render. That moves work that used to run or be deferred to the client into the server render step — reducing client fetch/hydration overhead for CPU‑heavy modules such as codecs, image processors, or complex data transforms. (github.com)
- Tooling stability: the Rolldown update to 1.0.0‑rc.4 (the Rust-powered Rollup-like bundler used by Vite) tightens compatibility and fixes bundling edge cases that affect WASM and SSR outputs; projects that rely on deterministic server bundles should see fewer transform/runtime mismatches. (github.com)
- Practical win for server rendering: by initialising Wasm on the server you avoid an extra network request and reduce early‑time-to-interactive for pages that depend on binary modules; this is especially useful for SSR frameworks and middleware that need deterministic, CPU-bound work during render.
Immediate checklist for teams (concise)
- Try the beta in a branch or staging CI: run your SSR build and server preview to validate .wasm imports behave as expected in your hosting runtime (Node/Bun/edge worker). (github.com)
- Audit asset sizes and initialization work: pre-initialising large Wasm modules on the server changes memory and CPU characteristics — measure cold start and memory usage in your environment.
- Validate bundler/rollup plugin behavior: if you use plugins that transform or wrap .wasm assets, confirm they work with the new Rolldown RC and Vite beta.
- Pin or gate upgrades in CI: use feature flags or canary deployments; betas are valuable for integration testing but not yet for mass production.
Bottom line This Vite beta is a practical, developer-facing change: it makes server-side WebAssembly a first-class citizen in Vite’s SSR flow and aligns the bundler stack with the Rust-based Rolldown release candidates. Teams using Wasm in web apps — especially those with server rendering or edge-rendered pages — should test the beta to understand performance and operational tradeoffs before promoting it to production. (github.com)
Source:
Source
Read Next
Svelte 5.52.0 adds TrustedHTML support for {@html}, enabling safer Trusted Types integration
February 21, 2026Svelte 5.52.0 (Feb 18, 2026) adds TrustedHTML support to {@html} expressions so apps can interoperate with browser Trusted Types without string coercion—important for XSS-hardening in SSR and client-rendered apps.
Next.js 16 makes Turbopack stable and the default for dev and build
February 20, 2026Next.js 16 moves Turbopack to stable/default, raises the Node.js minimum, and ships production-facing caching primitives — what full‑stack teams must change now.
React Native 0.84 Released — Hermes V1 Becomes the Default, Prebuilt iOS Binaries and Legacy‑Arch Removal
February 18, 2026React Native 0.84 makes Hermes V1 the default JavaScript engine, ships precompiled iOS binaries by default, removes remaining Legacy Architecture components, and raises the Node requirement — immediate actions for full‑stack teams.