cypress
16.3.0 · 10 Nov 2026MIT7.6M / weekRepositoryHomepagenpmAtom feed
Where each line stands
Plan an upgradeLatest releases
All 289 releases- 16.x · latest line
16.3.0
10 Nov 2026- Security
Upgraded
electronfrom41.7.0to43.8.4to address the compromised eMudhra intermediate certificates vulnerability reported in security scans. Connections that Cypress makes itself, such as to Cypress Cloud, now reject certificates issued through these intermediates. Node code in the config process, such as setupNodeEvents, runs on the Node.js version that runs thecypressCLI, so it needs a Node.js release that includes the same fix. Addresses #35124. - Security
Upgraded
systeminformationto5.33.18to address the SNYK-JS-SYSTEMINFORMATION-21771271 (CVE-2026-116576) vulnerability reported in security scans. Addresses #35196. - Security
Upgraded
node-forgefrom1.4.0to1.4.3to address the Improper Certificate Validation vulnerability reported in security scans. Addressed in #35279.
16.3.0
Released Nov 10, 2026
Performance:
In
cypress run, specs now start sooner when Cypress launches a new browser for them. In Electron, this is every spec unless component testing'sexperimentalSingleTabRunModeis enabled. In other browsers, it is the first spec and any spec after the browser exits unexpectedly. Fixed in #35186.The Cypress binary no longer includes a copy of TypeScript that it never used, since Cypress loads TypeScript from your project. This makes the download smaller and takes less disk space once installed. On Linux arm64, Cypress also starts faster, because it no longer tries to load TypeScript as it launches. Fixed in #35184.
cypress runnow spends less time finding the browsers installed on your machine before it starts the first spec, so runs start sooner. Fixed in #35181.Installing the Cypress binary from an interactive terminal, such as with
npx cypress install, now finishes unzipping sooner and uses less CPU, especially on Windows. Installs in CI, and package manager installs that run without a terminal, are unchanged. Fixed in #35243.
Features:
Registering the same event more than once in setupNodeEvents now runs every handler in registration order, instead of only the last one, for before:run, after:run, before:spec, after:spec, before:browser:launch, and after:screenshot.
before:browser:launchandafter:screenshothandlers each receive the result of the handler before them. If a handler throws, later handlers do not run. If you re-registered one of these events to replace a plugin's handler, both now run; to keep only yours, pass the plugin anonthat skips that event. Addresses #5240, #19809 and #27524.
Bugfixes:
Fixed a regression in 16.0.0 where changes a cy.intercept() response handler made to
Set-Cookieheaders did not reach the browser in Chromium-based browsers. The browser stored the cookies exactly as the server sent them, so a handler that rewrote a cookie's attributes, such as addingSameSite=Noneso a cross-site login cookie is accepted, or that removed a cookie, had no effect. Cookies in the browser now match theSet-Cookieheaders the handler leaves on the response. Fixes #34902.Fixed an issue where Cypress could use a port that browsers refuse to load, such as 10080, when the port option was not set. The runner then failed with
ERR_UNSAFE_PORT. Cypress now redraws a blocked randomly assigned port, and a blocked port in configuration is reported as a configuration error that names the port before the runner server starts. Fixes #30869.Fixed an issue where a spec whose bundled file includes a large inline source map could crash the browser tab, leaving
cypress runhanging with no error until it was killed. The crash could happen while the spec first loaded, or when it loaded again after its first cy.visit() to another origin. Specs with inline source maps now also load faster and use less memory. Fixes #35201.Fixed an issue where
cypress runcould hang until it was killed, or exit with an unrelatedsocket hang uperror, when the process that loads your config file and runs your Node events exited, for example because the operating system ran out of memory orsetupNodeEventscalledprocess.exit(). In component testing this process also runs the dev server. Cypress now stops the run with an error that says the process exited, with its exit code or signal. Fixes #25507 and #35223.Fixed an issue where, in Chrome 158 and later,
cypress runstopped with the error* is not a valid URLwhen it opened a second spec. Fixes #35195.Fixed an issue where, in Chrome 158 and later with injectDocumentDomain enabled, navigating the application under test within cy.origin() could fail with errors such as
Blocked a frame with originordoes not have permission to navigate the target frame. Chrome 158 stopped firingunloadevents, which Cypress uses to track navigations. Fixed in #35198.Fixed an issue where cy.intercept() silently ignored a header matcher when the same header name appeared more than once with different casing, such as
Content-Typeandcontent-type. Only the last matcher was applied.cy.intercept()now throws an error that names the duplicated header. Fixes #34975.The error shown when Cypress cannot start on Linux because of a missing system library now lists each library and the package that provides it, and a missing or failing Xvfb now shows install commands or the likely causes. Addressed in #35116.
Fixed an issue where
cypress tapcommands could delete the record of a runningcypress opensession, and report that no session was running, when run from a process that cannot see the session's process ID, such as a different PID namespace in a container or sandbox. The record is now kept while the session responds. Fixed in #35103.cypress opennow prints configuration errors and warnings, including the stack trace of a config file that fails to load, to the terminal. Previously they only appeared in the Cypress window, so a script or AI agent runningcypress opensaw nothing while it waited. Fixed in #35104.cypress open --project <path> --e2e --browser <browser>run by an AI coding agent now launches the browser without waiting for the welcome screen to be dismissed in the Cypress window. SetCYPRESS_AGENT_MODE=1to force this behavior for an agent Cypress does not detect, orCYPRESS_AGENT_MODE=0to turn it off. Fixed in #35105.cypress open --e2e --project <path>run by an AI coding agent in a project with no Cypress configuration file now creates the configuration and support files and starts the project in one launch, and prints the files it created. Previously the project did not start until Continue was pressed in the Cypress window. Fixed in #35106.cypress tap statusnow reports anerrorstage, with the reason, whencypress opencould not load the project, for example because the configuration file has a syntax error, and the othercypress tapcommands say that the project could not load instead of that no session is running. Previouslycypress tap statusreportednot connected. Fixed in #35107.When the path given to
--browseris not recognized as a browser, the warning now includes what running the path with--versionprinted, so a missing library or an unsupported binary can be told apart. Fixed in #35108.Fixed an issue where
cypress opendid not open the app window when theELECTRON_RUN_AS_NODEenvironment variable was set, as in some AI agent environments.cypress opennow ignores the variable and prints a warning, whilecypress runstill honors it. Fixed in #35111.Fixed an issue where the Cypress app started with
cypress open --detachedcould stop working or exit shortly after the command returned, particularly on Linux where Cypress starts its own virtual display. The app's output is now written to files in the system temp directory, and the command prints where those files are. Because the virtual display now keeps running with the app,cypress open --detachedno longer uses the display set byXVFB_DISPLAY_NUM, and prints a warning when it is set. Fixed in #35112.Fixed an issue where installing the Cypress binary could hang or fail outright when the connection was reset or the download server returned a temporary error. The download is now retried up to 3 times with an increasing delay before the install fails. Fixed in #35115.
Fixed an issue where
cypress openandcypress runon Linux failed to start with a "Missing X server or $DISPLAY" error whenDISPLAYpointed to an X server that was not running. Cypress now starts its own Xvfb and retries. Fixed in #35114.Improved the
--helpoutput ofcypress tapand its subcommands to identify arguments and flags that are required or have dependencies on others. Fixed in #35227.When the Cypress binary cannot be saved while it downloads, such as when the disk is full, cypress install and
npm install cypressnow fail with the underlying error, such asENOSPC: no space left on device, and delete the partially downloaded file, instead of crashing with a Node.js stack trace and leaving the file behind in the temporary folder. Fixed in #35219.Fixed an issue where, in
cypress openandcypress run, the browser launched by Cypress kept loading forever with no error when the Cypress installation was missing some of its files. Cypress now shows an error that names the missing file after a few seconds. Fixed in #35232.Fixed an issue where, in
cypress runwith Firefox, a spec where the browser never connected caused the next spec to crash the whole run. The next spec now launches a new browser. Failed attempts to connect to Firefox also no longer leave Firefox processes running. Fixed in #35246.Fixed an issue where the browser tab running Cypress could stop responding when a test's command log held an object with a circular reference reachable by more than one path, such as an object passed to cy.wrap() or stubbed with cy.stub(). Fixes #35231.
Fixed an issue where cy.scrollTo() and .scrollIntoView() ignored a
durationgiven as a string, such as'2000', and always animated the scroll for 400ms. A stringdurationis now read as milliseconds, the same as a number. Fixed in #35248.Fixed an issue where .select() did not fire
inputandchangeevents on a<select multiple>when the selection changed but its first selected option stayed the same, such as selecting['apple', 'banana']whenapplewas already selected. Fixed in #35254.Fixed an issue where
cypress runin Firefox on Windows could print part of anEPERMerror, such ascode: 'EPERM'andsyscall: 'rm', after the run finished. The error came from deleting the Firefox profile while Firefox still had files in it open. Cypress now retries the deletion, and if the profile still cannot be deleted, it no longer prints an error and a latercypress runcan remove the profile. Fixes #35293.Fixed an issue where an assertion's failure message showed the wrong value when the value being asserted on, the expected value, or the actual value contained
#{this},#{act}or#{exp}. For example,expect('#{exp}').to.equal('x')failed withexpected ''x'' to equal 'x', and now fails withexpected '#{exp}' to equal 'x', both in the error and in the Command Log. Fixed in #35301.Fixed an issue where an assertion failed with an unrelated
TypeErrorinstead of its own message when the value had adocumentgetter that threw something other than anError. Fixed in #35301.Fixed an issue where cy.fixture() did not cache a fixture whose content is empty or falsy, such as an empty
.txt,.csv, or.htmlfile, or a.jsonfile that contains only0,false,"", ornull. Every call read the file from disk again, so each call could time out, and a later call could yield different content if the file had changed since the first call. These fixtures are now cached like any other fixture. A.jsfixture that evaluates toundefinednow yieldsundefinedinstead of failing with"undefined" is not valid JSON. Fixed in #35327.
Misc:
The TypeScript types for .scrollIntoView() no longer accept the
ensureScrollableoption, which only cy.scrollTo() uses..scrollIntoView()always ignored it, so TypeScript code that passesensureScrollableto.scrollIntoView()now fails to compile. Remove the option to fix the error; scrolling behaves the same without it. Addressed in #35331.The error shown when cy.session() is passed an unknown option now lists every valid option,
cacheAcrossSpecsandvalidate. Previously it listed onlyvalidate, suggesting thatcacheAcrossSpecswas not a valid option. Addressed in #35233.The editor chooser now lists only the editors Cypress detects, and the Custom option has been removed. To use an editor that isn't listed, set the
LAUNCH_EDITORenvironment variable before starting Cypress. Addressed in #35208.
Dependency Updates:
- Security
Upgraded
electronfrom41.7.0to43.8.4to address the compromised eMudhra intermediate certificates vulnerability reported in security scans. Connections that Cypress makes itself, such as to Cypress Cloud, now reject certificates issued through these intermediates. Node code in the config process, such as setupNodeEvents, runs on the Node.js version that runs thecypressCLI, so it needs a Node.js release that includes the same fix. Addresses #35124. Upgraded bundled Node.js version from
24.15.0to24.22.1. Addresses #35124.Upgraded bundled Chromium version from
146.0.7680.216to150.0.7871.250. Addresses #35124.- Security
Upgraded
systeminformationto5.33.18to address the SNYK-JS-SYSTEMINFORMATION-21771271 (CVE-2026-116576) vulnerability reported in security scans. Addresses #35196. - Security
Upgraded
node-forgefrom1.4.0to1.4.3to address the Improper Certificate Validation vulnerability reported in security scans. Addressed in #35279. - Security
Upgraded
jimpfrom0.22.12to1.6.1to address an infinite loop vulnerability (CVE-2026-31808) in itsfile-typedependency reported in security scans. This also removesxml2js0.4.23, which has a prototype pollution vulnerability (CVE-2023-0842). Addresses #35271.
16.2.1
28 Oct 202616.2.0
14 Oct 2026- Security
Upgraded
shell-quotefrom1.10.0to1.11.0to address a Command Injection vulnerability reported in security scans.shell-quoteis a transitive dependency oflaunch-editor. Addressed in #34960. - Security
Upgraded
simple-gitfrom3.36.0to4.0.2to address a Command Injection vulnerability and two Arbitrary Command Injection vulnerabilities (SNYK-JS-SIMPLEGIT-20335524, SNYK-JS-SIMPLEGIT-20335540) reported in security scans. This also upgrades its@simple-git/argv-parserdependency from1.1.1to2.0.1, which addresses a Command Injection vulnerability reported in security scans. Addressed in #34960. Added the cy.getByRole() query, which finds elements by their ARIA role and, optionally, their accessible name, for example
cy.getByRole('tab', { name: 'Billing' }). Elements hidden from the accessibility tree are skipped unless you pass{ hidden: true }. For a role that HTML has an element for, only that element matches by default, socy.getByRole('button')finds a<button>but not a<div role="button">. Pass{ native: false }to also match elements with aroleattribute. Like cy.get(), it yields every match and retries until its assertions pass. When nothing matches, the error lists the roles and accessible names on the page. Addressed in #34937.
16.2.0
Released Oct 13, 2026
Features:
Added the cy.getByRole() query, which finds elements by their ARIA role and, optionally, their accessible name, for example
cy.getByRole('tab', { name: 'Billing' }). Elements hidden from the accessibility tree are skipped unless you pass{ hidden: true }. For a role that HTML has an element for, only that element matches by default, socy.getByRole('button')finds a<button>but not a<div role="button">. Pass{ native: false }to also match elements with aroleattribute. Like cy.get(), it yields every match and retries until its assertions pass. When nothing matches, the error lists the roles and accessible names on the page. Addressed in #34937.
Bugfixes:
Fixed a regression in 16.0.0 where a configured clientCertificates entry was not presented for requests the browser issued in Chrome, Chromium, and Edge, so an origin requiring mutual TLS showed a certificate prompt in
cypress openand hung incypress run. Fixes #34807.Fixed a regression in 15.20.0 where a cookie changed by cy.request() or cy.setCookie() was sent to the server with its earlier value on the next navigation of the application under test, even though cy.getCookie() reported the new one. Fixes #34891.
Fixed a regression in 15.0.0 where cy.go() finished before the page it navigated to had loaded. The next command could run against the page being navigated away from, so tests that went back or forward could fail intermittently.
cy.go()also yieldedundefinedinstead of the window, and ignored itstimeoutoption and pageLoadTimeout.cy.go()now waits for the page to load, yields the window, and fails if the page does not load within the timeout. Fixes #32460.Fixed a regression in 15.0.0 where output written to stderr from your config file, such as
console.error()insetupNodeEvents, could intermittently be missing from the terminal output ofcypress runwhen written right after another line. Fixed in #35022.cy.get() now fails right away when you ask for index
0of a cy.intercept() alias, such ascy.get('@getUsers.0'). Previously, Cypress retried until the command timed out before it showed the error, even though retrying could never succeed. Fixed in #34936.Fixed an issue where chapter markers in videos recorded during
cypress runin Chrome-based browsers, Electron, and Firefox were placed later than the tests they label when the browser was slow to show its first frame. In that case the video could also report a longer length than its footage and show a frozen final frame. Fixed in #35018.Fixed an issue where an error whose
messagecannot be overwritten — such as theDOMExceptiona browser throws for a cross-origin access or a Content Security Policy violation — was reported asTypeError: setting getter-only property "message"from inside Cypress, hiding the error that actually failed the test. Fixes #34818.Fixed an issue where, after one request missed its browser pre-request, every later request with the same method and URL waited the full 2 second pre-request timeout for the rest of the spec. Fixes #34966.
Fixed an issue where cy.prompt and Studio could fail to load. Fixed in #35013.
Calling a query that needs a subject, such as .eq(), .first(), .find(), or .shadow(), directly off
cyinstead of chaining it off a command that yields a subject now fails right away with an error that names the command and explains that it must be chained. Previously, Cypress retried until the command timed out and then reported that the subject was not a DOM element, or, when the query was the first command in a test, failed withCannot read properties of undefined (reading 'get'). Child commands called directly offcy, such ascy.click(), show the same reworded error. Fixed in #35024.Fixed an issue where
cypress runchanged the browser thatcypress openselects by default for a project to whichever browser the run used, such as the one passed with--browser. Fixed in #34924.
Misc:
TypeScript now types the object yielded by cy.location() as the plain object Cypress actually yields, instead of the browser's
window.location.searchParamsis now typed, socy.location('searchParams')andloc.searchParams.get('q')no longer report a type error. Addressed in #34956.Masked the environment variable values on the Project settings page. Addressed in #35004.
Dependency Updates:
- Security
Upgraded
shell-quotefrom1.10.0to1.11.0to address a Command Injection vulnerability reported in security scans.shell-quoteis a transitive dependency oflaunch-editor. Addressed in #34960. - Security
Upgraded
simple-gitfrom3.36.0to4.0.2to address a Command Injection vulnerability and two Arbitrary Command Injection vulnerabilities (SNYK-JS-SIMPLEGIT-20335524, SNYK-JS-SIMPLEGIT-20335540) reported in security scans. This also upgrades its@simple-git/argv-parserdependency from1.1.1to2.0.1, which addresses a Command Injection vulnerability reported in security scans. Addressed in #34960.
Dependency tracking
Know when your own dependencies move
cypress shipped a new major in the last 12 months, among 30 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 20 Nov 2026. Releases and advisories last read 20 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.