You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the release of Angular 17, Vite has become an officially supported bundler, and many Angular applications are transitioning from Webpack to Vite. To maintain consistency in the development stack, it would be beneficial if Cypress supported Vite for component testing in Angular applications. This would allow developers to use the same bundler for their application, e2e tests, and component tests, streamlining the workflow and improving efficiency.
Why is this needed?
Providing Vite support for component testing in Angular applications would align with the growing adoption of Vite and ensure a unified testing and development experience. It would help developers avoid potential bundling discrepancies and reduce the complexity of managing different bundlers for various testing scenarios.
Other
No response
The text was updated successfully, but these errors were encountered:
I would also like to add that Esbuild + Vite is now the default bundler-dev-server combo when generating a new Angular application as of atleast version 19.
Additionally the Angular teams recommends migrating existing application with an automated migration script.
It really seems like the Angular team is doing everything they can to get people to move away from Webpack.
Anecdotally the product I work is currently migrating to Esbuild and Vite and Cypress component tests are the only place where Webpack is still being used.
What would you like?
With the release of Angular 17, Vite has become an officially supported bundler, and many Angular applications are transitioning from Webpack to Vite. To maintain consistency in the development stack, it would be beneficial if Cypress supported Vite for component testing in Angular applications. This would allow developers to use the same bundler for their application, e2e tests, and component tests, streamlining the workflow and improving efficiency.
Why is this needed?
Providing Vite support for component testing in Angular applications would align with the growing adoption of Vite and ensure a unified testing and development experience. It would help developers avoid potential bundling discrepancies and reduce the complexity of managing different bundlers for various testing scenarios.
Other
No response
The text was updated successfully, but these errors were encountered: