Vue 4 Enters Planning with Promise of Backward Compatibility and Full ESM Switch

Dropping CommonJS will force build and bundler updates across the Vue ecosystem, but the backward-compatibility pledge reduces the risk of a painful migration. The broader point: AI coding is repositioning front-end developers from hands-on coders to product-focused decision-makers, so investing in judgment and product sense is the practical hedge.

Vue 4 is officially on the planning table. Evan You outlined the direction at Vue Fes Japan 2026 in Tokyo: no large breaking changes to preserve ecosystem compatibility, a full migration to ES modules that drops CommonJS builds, and a set of new features still in RFC. No release date has been set.

The Vue ecosystem is also evolving beyond the next major version. Vue 3.6 is working on Vapor Mode, a new compilation strategy that reduces reliance on the virtual DOM by generating more direct DOM update logic, promising lower runtime overhead and improved performance. Evan You's tooling efforts now span Vite, Rolldown, and Vite+, pushing the broader JavaScript toolchain forward.

The conversation around Vue 4 also touches on AI coding's role in front-end development. Manual component splitting, styling, and API wiring are increasingly handled by AI tools, shifting the developer's primary job from writing code to exercising judgment. The original commentary stresses that in the AI era, judgment paired with AI outweighs raw coding skill, and the ability to understand requirements and design products remains the durable asset.