@cypress/schematic
6.0.0 · 26 Aug 2026MIT116k / weekRepositoryHomepagenpmAtom feed
Where each line stands
Plan an upgradeLatest releases
All 38 releases- 6.x · latest line
6.0.0
26 Aug 2026- Deprecated
cy.server()andcy.route()have been deprecated. In a future release, support forcy.server()andcy.route()will be moved to a plugin. We encourage you to usecy.intercept()instead. Addressed in #9185. - Deprecated
experimentalFetchPolyfillhas been deprecated. We encourage you to usecy.intercept()to intercept requests using the Fetch API instead. Cypress now always throws an error when asserting on an element that doesn't exist in the DOM (unless you're asserting that the element should
not.exist). Assertions such asnot.visible,not.contains,not.have.class, etc will now fail when used on non-existent DOM elements. Addresses #205.
Released 11/23/2020
Summary:
Cypress now offers full network stubbing support with the introduction of the
cy.intercept()command (previouslycy.route2()). Withcy.intercept()your tests can intercept, modify and wait on any type of HTTP request originating from your app.Breaking Changes:
Please read our Migration Guide which explains the changes in more detail and how to change your code to migrate to Cypress 6.0.
Cypress now always throws an error when asserting on an element that doesn't exist in the DOM (unless you're asserting that the element should
not.exist). Assertions such asnot.visible,not.contains,not.have.class, etc will now fail when used on non-existent DOM elements. Addresses #205.DOM elements where the CSS style (or ancestors) are
opacity: 0are no longer considered visible. However these are still considered actionable and "any action commands" interacting-with-elements#Actionability used to interact with the element will perform the action. This matches browser's implementation on how they regard elements withopacity: 0. Addresses #4474.The type yielded by
cy.wait(alias)has changed in order to support use ofcy.intercept(). Addressed in #9266.The
experimentalNetworkStubbingoption has been removed and made the default behavior. You can safely removed this configuration option. Addressed in #9185.When using
.type()and.click()on elements inside acontenteditableelement, the events are now properly triggered on the inside elements. This may cause unintended consequences if you were relying on the previous behavior. Addressed in #9066.We removed several deprecation errors around APIs that were removed in versions of Cypress prior to 4.0.0. This will not cause any changes for anyone upgrading from a 4.0+ version of Cypress. For a full list of all APIs affected see #8946.
We updated our HTTP status codes and reason phrases to match Node.js
http.STATUS_CODES. If you have code that relies on a reason phrase, then this could affect you. Addressed in #8969.JSON request and response bodies captured by
cy.intercept()are now automatically parsed, removing the need to manually doJSON.parse. Addressed in #9280.
Deprecations:
Deprecations still work as before but will be removed from Cypress in a future release. We encourage you to update your code now to remove uses of deprecations.
- Deprecated
cy.server()andcy.route()have been deprecated. In a future release, support forcy.server()andcy.route()will be moved to a plugin. We encourage you to usecy.intercept()instead. Addressed in #9185. - Deprecated
experimentalFetchPolyfillhas been deprecated. We encourage you to usecy.intercept()to intercept requests using the Fetch API instead. cy.route2()was renamed tocy.intercept(). We encourage you to update usages ofcy.route2()to usecy.intercept(). Addressed in #9182.
Features:
The new
cy.intercept()command can be used to manage the behavior of HTTP requests at the network layer. Addressed in #9182.We now pass
—disable-dev-shm-usageto the Chrome browser flags by default. This will write shared memory files into/tmpinstead of/dev/shm. If you're passing this flag in yourpluginsfile, you can now remove this code. Addresses #5336.A warning is now displayed when passing invalid configuration keys through the CLI. Addresses #428.
The
cypress versioncommand now also displays the current Electron and bundled Node versions. Addresses #9180.The
cypress versioncommand now accepts a--componentflag that allows you to print the version of specific components of Cypress. ie Electron, Node, etc. Addresses #9214.
Bugfixes:
We fixed a regression introduced in 3.5.0 that would cause
.type()to not type the entire string when focus was called away from the target element. Fixes #9254..type()and.click()now properly work on elements inside acontenteditableelement. Fixes #2717 and #7721.We fixed a regression introduced in 5.6.0 that would cause the Test Runner to crashes and display a white page when switching tabs while tests are running. Fixes #9151.
Fixed an issue where
Content-Lengthforcy.route2request bodies could be incorrectly recalculated. Fixes #9166.
Documentation Changes:
Our Migration Guide has a new section for 6.0 migration.
Many of our docs examples have been updated to use
cy.intercept()in place ofcy.route()including our Network Requests doc.
Misc:
Added the type of
redirectsand changedredirectedToUrloptional for Response types. Addresses #9275.
Dependency Updates
- 5.x · maintenance
5.0.0
19 Dec 2025- Deprecated
The
cypress-plugin-retriesplugin has been deprecated in favor of test retries built into Cypress. Addresses #1313. - Breaking
Cypress no longer supports file paths with a question mark
?in them. We now use the webpack preprocessor by default and it does not support files with question marks. Addressed in #7982. - Breaking
Cypress now requires TypeScript 3.4+. Addressed in #7856.
Released 8/19/2020
Summary:
Cypress now includes support for test retries! Similar to how Cypress will retry assertions when they fail, test retries will allow you to automatically retry a failed test prior to marking it as failed. Read our new guide on Test Retries for more details.
Breaking Changes:
Please read our Migration Guide which explains the changes in more detail and how to change your code to migrate to Cypress 5.0.
- Deprecated
The
cypress-plugin-retriesplugin has been deprecated in favor of test retries built into Cypress. Addresses #1313. The
Cypress.Cookies.defaults()whitelistoption has been renamed topreserveto more closely reflect its behavior. Addressed in #7782.The
blacklistHostsconfiguration has been renamed toblockHoststo more closely reflect its behavior. Addressed in #7622.The
cy.server()whitelistoption has been renamed toignoreto more closely reflect its behavior. Addresses #6642.libgbm-devis now a requirement to run Cypress on Linux. Addressed in #7791.Values yielded by
cy.setCookie(),cy.getCookie(), andcy.getCookies()will now contain thesameSiteproperty if specified. Addresses #6892.The
experimentalGetCookiesSameSiteconfiguration flag has been removed, since this behavior is now the default. Addresses #6892.The return type of the
Cypress.BlobmethodsarrayBufferToBlob,base64StringToBlob,binaryStringToBlob, anddataURLToBlobhave changed fromPromise<Blob>toBlob. Addresses #6001.- Breaking
Cypress no longer supports file paths with a question mark
?in them. We now use the webpack preprocessor by default and it does not support files with question marks. Addressed in #7982. For TypeScript compilation of spec, support, and plugins files, the
esModuleInteropoption is no longer coerced totrue. If you need to utilizeesModuleInterop, set it in yourtsconfig.json. Addresses #7575.- Breaking
Cypress now requires TypeScript 3.4+. Addressed in #7856.
- Breaking
Installing Cypress on your system now requires Node.js 10+. Addresses #6574.
In spec files, the values for the globals
__dirnameand__filenameno longer include leading slashes. Addressed in #7982.
Features:
.click(),.dblclick(), and.rightclick()now accept optionsaltKey,ctrlKey,metaKey, andshiftKeyto hold down key combinations while clicking. Addresses #486.You can now chain
.snapshot()off ofcy.stub()andcy.spy()to disabled snapshots during those commands. For example:cy.stub().snapshot(false). Addresses #3849.
Bugfixes:
The error
Cannot set property 'err' of undefinedwill no longer incorrectly throw when rerunning tests in the Test Runner. Fixes #7874 and #8193.Cypress will no longer throw a
Cannot read property 'isAttached' of undefinederror duringcypress runon Firefox versions >= 75. Fixes #6813.The error
Maximum call stack size exceededwill no longer throw when callingscrollIntoViewon an element in the shadow dom. Fixes #7986.Cypress environment variables that accept arrays as their value will now properly evaluate as arrays. Fixes #6810.
Elements having
display: inlinewill no longer be considered hidden if it has child elements within it that are visible. Fixes #6183.When
experimentalShadowDomSupportis enabled,.parent()and.parentsUntil()commands now work correctly in shadow dom as well as passing a selector to.parents()when the subject is in the shadow dom. Fixed in #8202.Screenshots will now be correctly taken when a test fails in an
afterEachorbeforeEachhook after the hook has already passed. Fixes #3744.Cypress will no longer report screenshots overwritten in a
cy.screenshot()onAfterScreenshotoption as a unique screenshot. Fixes #8079.Taking screenshots will no longer fail when the screenshot names are too long for the filesystem to accept. Fixes #2403.
The "last used browser" will now be correctly remembered during
cypress openif a non-default-channel browser was selected. Fixes #8281.For TypeScript projects,
tsconfig.jsonwill now be loaded and used to configure TypeScript compilation of spec and support files. Fixes #7006 and #7503.reporterStatsnow correctly show the number of passed and failed tests when a test passes but theafterEachfails. Fixes #7730.The Developer Tools menu will now always display in Electron when switching focus from Specs to the Test Runner. Fixes #3559.
Documentation Changes:
We have a new guide on Test Retries.
Our Migration Guide has a new section for 5.0 migration.
Misc:
Cypress now uses the webpack preprocessor by default to preprocess spec files.
The Runs tab within the Test Runner has a new improved design when the project has not been set up or login is required. Addressed in #8141.
The type for the
Windowobject returned fromcy.window()is now correct. Addresses #7856.The type definition for Cypress's
ApplicationWindowcan now be extended. Addresses #7856.The type definition for
reporterOptionshas been added. Addresses #7877.
Dependency Updates
Upgraded Chrome browser version used during cypress run and when selecting Electron browser in cypress open from
80to83. Addressed in #7791.Upgraded bundled Node.js version from
12.8.1to12.14.1. Addressed in #7791.Upgraded
chalkfrom2.4.2to4.1.0. Addressed in #7650.Upgraded
cli-table3from0.5.1to0.6.0. Addressed in #7650.Upgraded
electronfrom8.3.1to9.2.0. Addressed in #7791 and #8235.Upgraded
execafrom1.0.0to4.0.2. Addressed in #7650.Upgraded
expressfrom4.16.4to4.17.1. Addressed in #8179.Upgraded
fs-extrafrom8.1.0to9.0.1. Addressed in #7650.Upgraded
log-symbolsfrom3.0.0to4.0.0. Addressed in #7650.Upgraded
tmpfrom0.1.0to0.2.1. Addressed in #7650.
- 4.x · maintenance
4.3.0
5 Dec 2025Errors shown in the Test Runner have a new design including an expandable stack trace, better highlighting of code elements, and 'Learn more' links that link to relevant Cypress documentation. This is part of our larger improvements to error display with more exciting features to come. Addresses #3762.
When you open a Cypress project, clicking on the Settings tab and clicking into the Experiments panel will display the experimental features that are available and whether they are enabled for your project.
Added support for setting cookie
sameSitevalues viacy.setCookie(). Addresses #2437.
Released 3/30/2020
Features:
Errors shown in the Test Runner have a new design including an expandable stack trace, better highlighting of code elements, and 'Learn more' links that link to relevant Cypress documentation. This is part of our larger improvements to error display with more exciting features to come. Addresses #3762.
When you open a Cypress project, clicking on the Settings tab and clicking into the Experiments panel will display the experimental features that are available and whether they are enabled for your project.
Added support for setting cookie
sameSitevalues viacy.setCookie(). Addresses #2437.Added experimental support for adding
sameSitevalues to the objects yielded fromcy.setCookie(),cy.getCookie(), andcy.getCookies(). Users can enable this by setting theexperimentalGetCookiesSameSiteconfiguration value totrue. In Cypress 5, this will be the default. Addresses #2437.Added support for the
SameSitecookie attribute incy.request(),cy.visit(), and proxied HTTP requests. Addresses #6757.When an assertion is retried (using
.should()) and fails, it now shows the diff in thestdout. Addresses #6722.
Bugfixes:
Fixed a regression in 4.2.0 where cypress installation could fail if Git is not installed. Fixes #6752.
Fixed a regression in 3.5.0 where certain HTTP requests could fail with
Parse Error: Invalid header value charorParse Error: Header overflow. Fixes #5602.Fixed a regression in 4.2.0 where Electron deprecation warnings were printed to stderr in open mode. Fixes #6750.
Cookies set with a Domain containing an unknown TLD are now sent along for all requests. For example, a cookie like
foo=bar; Domain=.cypress.testwill now be sent during cy.request() tohttp://local.cypress.test. Fixes #6628.We fixed a situation where a cross-origin errors could incorrectly throw in Chrome. Fixes #5270.
Visibility checks against
vue-fragmentelements no longer throw an unexpected error. Fixes #6745.The stack trace is now properly shown in the console when clicking the command for tests having an
.onlythat throw an error. Fixes #6744.firefoxGcIntervalcan now correctly be set tonull. Fixes #6825.Cypress will no longer crash the process if an empty video chunk is received. Addressed in #6818.
Assertions failures on DOM elements no longer show unexpected diffs when they weren't retried. Fixes #6723.
Misc:
Security warnings no longer show in Mac OS when opening Cypress since our application now undergoes notarization from Apple. Addresses #5791.
The previously used spec filter in the Test Runner is now saved and restored for projects without an ID. Addresses #6739.
We collect more env information from Travis builds for potential use in the Cypress Dashboard. Addresses #6808.
We now collect env information from Netlify builds (for example when using {% url "cypress-io/netlify-plugin-cypress" github.com/cypress-io/netlify-plugin-cypress) to send along to the Cypress Dashboard. Addresses #6780.
Type added for
tagproperty when using Module API. Addresses #6795.We're continuing to make progress in converting our codebase from CoffeeScript to JavaScript. Addresses #2690 in #6833.
Dependency Updates
Upgraded Chrome browser version used during
cypress runand when selecting Electron browser incypress openfrom80.0.3987.141to80.0.3987.158. Addressed in #6855.Upgraded
electronfrom8.1.1to8.2.0. This bumps the bundled Chromium to80.0.3987.158. Addressed in #6855.Upgraded
@benmalka/foxdriverfrom0.2.3to0.3.0. Addressed in #6592.Upgraded
@cypress/get-windows-proxyfrom1.6.0to1.6.1. Addressed in #6823.Upgraded
execafrom1.0.0to4.0.0. Addressed in #6013.Upgraded
extract-zipfrom1.6.7to1.7.0. Addresses #6845 in #6845.Upgraded
firefox-profilefrom1.3.0to1.3.1. Addressed in #6594.Upgraded
get-portfrom5.1.0to5.1.1. Addressed in #6854.Upgraded
mimefrom1.6.0to2.4.4. Addressed in #6764.Upgraded
minimistfrom1.2.2to1.2.5. Addressed in #6747.Upgraded
squirrellyfrom7.7.0to7.9.2. Addressed in #6735.
Dependency tracking
Know when your own dependencies move
@cypress/schematic shipped 2 new majors in the last 12 months, among 4 releases. inlinr shows which of your projects are behind, and what the upgrade breaks.
Advisories reach you
An email when a critical or high advisory affects a project, before the next install.
Upgrades checked first
Peer ranges, Node, ESM-only and types changes read before you bump.
Only what matters
Majors and breaking notes stay; patches and sibling bumps fold into one line.
Reading releases, release notes and advisories…
Registry facts last checked 19 Nov 2026. Releases and advisories last read 21 Nov 2026.
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.