cypress
16.3.0 · 10 Nov 2026MIT7.6M / weekRepositoryHomepagenpmAtom feed
Upgrading cypress From 15.21.2 to 16.0.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 12
- changes to make
- 0
- advisories fixed
- 0
- new
- 4
- fixes
Start here
Before you upgrade
Tick each one off as you go- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Deprecated16.0.0
Release by release
- Breaking
Faster tests, less flake, and a few breaking changes that may require updates.
- Breaking
- Breaking
Removed the
cy.end()command, which ended a chain of commands by yieldingnull. A Cypress chain is already terminated when the nextcy.<command>()starts a new chain, so existing.end()calls can simply be removed. See the Migration Guide. Addressed in #33696. - Breaking
Removed the
experimentalSourceRewritingconfiguration option. The default regex-based source rewriting handles every case the AST-based rewriter did, so default behavior is unchanged and the option can be deleted from your config. If you were using it to work around Subresource Integrity errors, enable removeSRIAttributes instead. See the Migration Guide. Addresses #34213.
- Breaking
18 other lines we could not sort, mostly version bumps
- 16.0.0
Chrome, Chromium, and Edge intercept test traffic on the native browser network rather than routing it through Cypress. A small number of
cy.intercept()behaviors differ as a result. Most notably,req.httpVersionis no longer reported, and compression headers are no longer present on an intercepted response. Firefox, WebKit, and Electron continue to use the legacy network path, and forceHttp1 routes every browser back through it while you migrate. See Native network interception and the Migration Guide. Addresses #3708. - 16.0.0
Upgraded the bundled Node.js version from
22.19.0to24.15.0. Addressed in #33494. - 16.0.0
Removed
Cypress.env(). Use Cypress.expose() for non-sensitive values that need to be readable in the browser, and cy.env() for sensitive values that must remain in the Node process. Theenvkey is no longer supported in per-test or suite config overrides; useexpose: { KEY: value }instead if absolutely necessary. TheallowCypressEnvconfiguration option has also been removed. See the Migration Guide. Addresses #33889. Addressed in #33963. - 16.0.0
Removed the cy.exec() command and the
execTimeoutconfiguration option, both deprecated in Cypress15.21.0. Use cy.task() andtaskTimeoutinstead — a task runs in Node without depending on the operating system, shell, or terminal of the machine running Cypress. Callingcy.exec()now throws, and settingexecTimeoutprints a warning and is otherwise ignored. See the Migration Guide. Addresses #34694. - 16.0.0
The
experimentalMemoryManagementconfiguration option has graduated out of experimental status and been replaced by manageBrowserMemory, which defaults totrue. Memory management is now enabled by default in Chromium-based browsers. SettingexperimentalMemoryManagementprints a warning and is otherwise ignored. If you previously setexperimentalMemoryManagement: falseto opt out, you must now setmanageBrowserMemory: false. See the Migration Guide. Addresses #34385. - 16.0.0
The default
keystrokeDelayfor cy.type() has been changed from10to0to improve performance of typing-heavy test runs. Users who relied on the implicit 10ms delay can restore it by settingkeystrokeDelay: 10in their Cypress configuration or via Cypress.Keyboard.defaults(). Addresses #33523. - 16.0.0
cy.getCookie(), cy.getCookies(), and cy.getAllCookies() are now retry-able query commands. They re-read cookies and retry any chained assertions until they pass or time out, are governed by defaultCommandTimeout, and can no longer be overwritten with Cypress.Commands.overwrite(). Use Cypress.Commands.overwriteQuery() instead. See the Migration Guide. Addresses #4802.
- 16.0.0
viewportWidth and viewportHeight can no longer be set via Cypress.config() during test execution. Setting them this way affected the next test rather than the current one and was not reflected in Test Replay. Use cy.viewport() or set them in the test configuration of a
describe,context, oritblock instead. See the Migration Guide. Addresses #31592. Addressed in #34262. - 16.0.0
blockHosts can no longer be set via Cypress.config() during test execution. Setting it this way affected the next test rather than the current one. Set
blockHostsin the test configuration of adescribe,context, oritblock instead. See the Migration Guide. Addressed in #34553. - 16.0.0
cy.getAllLocalStorage() and cy.getAllSessionStorage() are now retry-able query commands. They re-read storage from all origins and retry any chained assertions until they pass or time out, accept a
timeoutoption governed by defaultCommandTimeout, and can no longer be overwritten with Cypress.Commands.overwrite(). Use Cypress.Commands.overwriteQuery() instead. See the Migration Guide. Addresses #26422. Addressed in #34318.
1 internal line (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.