electron-vite 5.0 is out!

December 7, 2025

electron-vite 5.0 is officially released today! This milestone version introduces multiple new features, optimizes core functionality, and thoroughly reorganizes the documentation, providing developers with a smoother and more efficient development experience.

• Github Changelog

Isolate Build

Isolated Build is designed to address common challenges in multi-entry application development, such as outputting a single file, efficient tree-shaking to avoid unnecessary module imports, and reducing excessive chunk generation.

electron-vite 5.0 introduces the build.isolatedEntries option, which enables automatic isolation of multiple entries and intelligent handling of shared chunks and asset outputs.

Use Cases:

• Main process: modules imported via ?modulePath have isolated builds enabled by default, with no configuration required.
• Preload scripts: if there are multiple entry points with shared imports, enabling isolated builds is necessary. This is a prerequisite for supporting the Electron sandbox (allowing output as a single bundle).
• Renderer process: Reduces the number of generated chunks, thereby improving rendering performance.

When there are many entry points in a project, enabling Isolated Build will increase build times, but this impact is typically within an acceptable range. The trade-off is well worth it: Isolated Build significantly improves application performance, enhances security, reduces development complexity, and increases developer productivity.

Enhanced string protection for Bytecode

In electron-vite 5.0, a brand-new Babel-based string protection plugin has been introduced for bytecode compilation, featuring the following protection enhancements:

• Compiles each string into a unique IIFE function, providing true obfuscation and making strings unreadable.
• Supports both string literals and template literals (static-only).

See bytecode.protectedStrings

Deprecations

1. externalizeDepsPlugin is deprecated, use build.externalizeDeps config option instead. In electron-vite 5.0, this behavior is enabled by default.

2. bytecodePlugin is deprecated, use build.bytecode config option instead.

Migrating to v5

For most projects, the update to electron-vite 5 should be straight forward. But we advise reviewing the detailed Migration Guide before upgrading.