-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Add a way to disable proxy #22319
Comments
I can't overstate what a massive improvement this would be, and I would be more than willing to help work on it. The performance penalty becomes even more pronounced in apps with a large number of chunks and other initial requests. Like @gajus suggests it seems unlikely that this cannot be handled inside the runtime environment itself rather than having an entire proxy layer between the browser and network. |
We are done with Cypress. Letting someone else advocate for this. |
Sad to hear that @gajus, may I know what you opted for instead? There has been some internal pressure here to move to Playwright (primarily for performance reasons) but we are lobbying hard to stay with Cypress ourselves. |
Yeah, no, moving away from Cypress to Playwright, while very painful, was the best decision we ever made. |
What would you like?
According to https://www.cypress.io/blog/2019/05/22/how-we-improved-network-speed-by-300-in-cypress-3-3-0/, Cypress proxies all requests in order to:
However, this comes at a major performance cost.
I would heavily prefer if Cypress did not proxy any requests, but instead provided a way to inject the necessary logic into the main application, e.g. as an NPM package.
Why is this needed?
This would drastically improve performance and reliability of Cypress tests.
The text was updated successfully, but these errors were encountered: