Cypress 15: Breaking changes

[jennifer-shehane]

What would you like?

This is just an issue to track potentially breaking changes for Cypress 15.

• Electron 34 upgrade (Node.js 22 upgrade) (what are the glibc implications?)
• Node.js 18 + 23 support removal
• ts-node removal (unsure if breaking)
• CDP code removal for Firefox (with BiDi being replacement and mainstream in Firefox v134)
• Removal of resourceType on cy.intercept (with replacement UI)
• Removal/deprecation of Cypress.runner.stop() (or change in behavior somehow)
• Remove injectDocumentDomain option
• With removal of injectDocumentDomain, we should change the default domain behavior of the Cypress cookie APIs to include subdomain (which is the standard implementation)
• Cypress Studio GA????

Component testing

• Remove support for Angular 17 (EOL security support 15 May 2025)
• Add support for Angular 20 (Estimated week of 19 May 2025)

Why is this needed?

No response

Other

No response

[MikeMcC399]

• Electron 34 upgrade (Node.js 22 upgrade) (what are the glibc implications?)

https://github.com/nodejs/node/blob/v22.12.0/BUILDING.md

I don't see any change for glibc.

[alexsch01]

Cypress.runner.stop() - why remove this?

[jennifer-shehane]

@alexsch01 We intend to keep this behavior of being able to stop execution of Cypress with an API, we're not sure if we'll maintain this API exactly.

Basically the way this is implemented does not play nicely with Test Replay. It immediately exits the process - and Test Replay is expecting a certain event to fire so it can upload the replay. When user's use this in a test to exit the runner (usually when a test fails), they end up with a completely blank Test Replay - and that's exactly when they'd like the data from Test Replay the most.

So we have to either update Cypress.runner.stop() to better handle this or if it can't, we'll need to add another API that plays better with Test Replay.