Cypress 15: Breaking changes

[jennifer-shehane]

What would you like?

We need to remove CDP support with Firefox removing CDP support in version 141 in June. This need is necessitating a breaking change. We want to include other relevant breaking changes for this release.

In Scope

• Firefox:
  • CDP code removal for Firefox (BiDi now mainstream with feat: implement webdriver BiDi for Firefox versions 135 and greater #30870 ) BREAKING CHANGE: Remove support for CDP within Firefox #31189
  • Cut over methods in @packages/extension that are firefox specific to use BiDi misc: Replace @packages/extension methods that are now implemented by WebDriver BiDi when BiDi is enabled #30221. Assess progress on milestone
• Replace ts-node with tsx for user configuration parsing and cypress runtime
  • Spike into removing ts-node [Spike] Investigate migrating off of ts-node #30426
  • Update @packages/data-context to use Stage 3 decorators chore: update decorators in @packages/data-context to use Stage 3 decorators or remove decorators entirely #31184
  • Replace ts-node with tsx for user configuration parsing and cypress runtime feat: replace ts-node with tsx for user configuration parsing and cypress runtime #31185
  • Allow for WBIP to take all of the users resolved config ts-loader in @cypress/webpack-batteries-included-preprocessor should respect all user compiler options #31282
  • Remove TypeScript 4 support BREAKING CHANGE: Remove support for TypeScript 4 #31187
• Feat: certain Cypress commands should not be bound to window in order to avoid cross origin issues Feat: certain Cypress commands should not be bound to window in order to avoid cross origin issues #31196
• Node.js 18 + 23 support removal Node.js 18 + 23 support removal #31302
• Electron 35 upgrade (Node.js 22 upgrade) (what are the glibc implications?) Electron Update (36) #31257
• Webpack 4 removal
• Webpack Dev Server 4 removal
• Remove migrations scripts for v9 -> v10 upgrades, etc
• Remove deprecated cy.stub signature
• Remove fallback polyfills in webpack-batteries-included-preprocessor Remove fallback polyfills in webpack-batteries-included-preprocessor #31039

Component testing

• Remove support for Angular 17 (EOL security support 26 May 2025) Remove Angular 17 support #31303
• Bump zone.js minimum dependency breaking: (@cypress/angular) bump minimum zone.js to 0.14.0 #31582
• Add support for Angular 20 (Estimated week of 19 May 2025) Angular 20 support #31304

Extra

• Fix any remaining Cy 14 issues before 15: https://github.com/cypress-io/cypress/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22v14.0.0%20%F0%9F%90%9B%22

[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.

[DobQA]

iFrame Support Finally would be good or some semi support.

[MikeMcC399]

Node.js 18 + 23 support removal

Node.js EOLs are:

Node.js	EOL
18.x	2025-04-30
23.x	2025-06-01

Currently

cypress/cli/package.json

Lines 122 to 124 in 6bd522b

	"engines": {
	"node": "^18.0.0 || ^20.0.0 || >=22.0.0"
	},

Should probably migrate to

"node": "^20.0.0 || ^22.0.0 || >=24.0.0"

with deprecation of Node.js 18 prior to Cypress 15