-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Vite 5 #335
Comments
Thanks for the reminder, it's under testing |
electron-vite 2 beta is out, welcome to test and report issues. |
After updating, rollup is no longer bundling dependencies for the main process. They're all being externalized. I'm using the split vendor chunk plugin. |
@shayded-exe You can set I will fix this issue. |
Hi, I am using the beta-4 version and the HMR is not working when i have vue router. In the console I receive a message that the component is updated but the browser is not updating |
Fixed with v2.0.0 |
electron-vite 2.0 is out! 🎉,check out Announcement Blog Post for details. |
This commit updates the `vite` dependency to the latest version (5.1.X) and makes necessary adjustments to accommodate deprecations and new features introduced in Vite 5.1.X. Changes include: - Modify the import statement for SVG files to use `query: '?raw'` syntax due to the deprecation of the `as: raw` option. - Update `moduleResolution` setting to `Bundler` in `tsconfig.json` to support the new TypeScript 5 option, aligning with Vite 5's migration guide for Rollup 4 compatibility without requiring file extensions on relative imports. Plugin migrations for Vite 5 support: - Bump `@modyfi/vite-plugin-yaml`, see @modyfi/vite-plugin-yaml#22. - Bump `electron-vite`, see alex8088/electron-vite#335. - Bump `vitejs/plugin-legacy`. - Bump `vitejs/vite-plugin-vue`, see vitejs/vite-plugin-vue#290.
Clear and concise description of the problem
Vite 5 is released but this package requires maximum of Vite 4.x as peer-dependency, blocking migrations to Vite 5.
Suggested solution
Support usage with Vite 5.
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: