Packages

cypress

16.3.0 · 10 Nov 2026MIT7.6M / weekRepositoryHomepagenpmAtom feed

Your version

16.3.0

Latest10 Nov 2026Where it was published

In short

4 breaking1 removed4 security4 faster28 fixed2 internal

  • Breaking

    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:launch and after:screenshot handlers each receive the result of the handler before them. If a han

  • Breaking

    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-Type and content-type. Only the last matcher was applied. cy.intercept() now throws an error that names the duplicated header.

  • Breaking

    Fixed an issue where the Cypress app started with cypress open --detached could 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 --detached no longer uses the display set by XVFB_DISPLAY_NUM, and prints a warning when it is set. Fixed.

  • Breaking

    The TypeScript types for .scrollIntoView() no longer accept the ensureScrollable option, which only cy.scrollTo() uses. .scrollIntoView() always ignored it, so TypeScript code that passes ensureScrollable to .scrollIntoView() now fails to compile. Remove the option to fix the error; scrolling behaves the same without it. Addressed.

  • Removed

    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_EDITOR environment variable before starting Cypress. Addressed.

  • Security

    Upgraded electron from 41.7.0 to 43.8.4 to 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 the cypress CLI, so it needs a Node.js release that includes the same fix. Addresses.

  • Security

    Upgraded systeminformation to 5.33.18 to address the SNYK-JS-SYSTEMINFORMATION-21771271 (CVE-2026-116576) vulnerability reported in security scans. Addresses.

  • Security

    Upgraded node-forge from 1.4.0 to 1.4.3 to address the Improper Certificate Validation vulnerability reported in security scans. Addressed.

Release note

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's experimentalSingleTabRunMode is 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 run now 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:launch and after:screenshot handlers 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 an on that 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-Cookie headers 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 adding SameSite=None so a cross-site login cookie is accepted, or that removed a cookie, had no effect. Cookies in the browser now match the Set-Cookie headers 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 run hanging 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 run could hang until it was killed, or exit with an unrelated socket hang up error, when the process that loads your config file and runs your Node events exited, for example because the operating system ran out of memory or setupNodeEvents called process.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 run stopped with the error * is not a valid URL when 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 origin or does not have permission to navigate the target frame. Chrome 158 stopped firing unload events, 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-Type and content-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 tap commands could delete the record of a running cypress open session, 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 open now 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 running cypress open saw 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. Set CYPRESS_AGENT_MODE=1 to force this behavior for an agent Cypress does not detect, or CYPRESS_AGENT_MODE=0 to 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 status now reports an error stage, with the reason, when cypress open could not load the project, for example because the configuration file has a syntax error, and the other cypress tap commands say that the project could not load instead of that no session is running. Previously cypress tap status reported not connected. Fixed in #35107.

  • When the path given to --browser is not recognized as a browser, the warning now includes what running the path with --version printed, so a missing library or an unsupported binary can be told apart. Fixed in #35108.

  • Fixed an issue where cypress open did not open the app window when the ELECTRON_RUN_AS_NODE environment variable was set, as in some AI agent environments. cypress open now ignores the variable and prints a warning, while cypress run still honors it. Fixed in #35111.

  • Fixed an issue where the Cypress app started with cypress open --detached could 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 --detached no longer uses the display set by XVFB_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 open and cypress run on Linux failed to start with a "Missing X server or $DISPLAY" error when DISPLAY pointed to an X server that was not running. Cypress now starts its own Xvfb and retries. Fixed in #35114.

  • Improved the --help output of cypress tap and 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 cypress now fail with the underlying error, such as ENOSPC: 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 open and cypress 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 run with 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 duration given as a string, such as '2000', and always animated the scroll for 400ms. A string duration is now read as milliseconds, the same as a number. Fixed in #35248.

  • Fixed an issue where .select() did not fire input and change events on a <select multiple> when the selection changed but its first selected option stayed the same, such as selecting ['apple', 'banana'] when apple was already selected. Fixed in #35254.

  • Fixed an issue where cypress run in Firefox on Windows could print part of an EPERM error, such as code: 'EPERM' and syscall: '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 later cypress run can 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 with expected ''x'' to equal 'x', and now fails with expected '#{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 TypeError instead of its own message when the value had a document getter that threw something other than an Error. 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 .html file, or a .json file that contains only 0, false, "", or null. 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 .js fixture that evaluates to undefined now yields undefined instead of failing with "undefined" is not valid JSON. Fixed in #35327.

Misc:

  • The TypeScript types for .scrollIntoView() no longer accept the ensureScrollable option, which only cy.scrollTo() uses. .scrollIntoView() always ignored it, so TypeScript code that passes ensureScrollable to .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, cacheAcrossSpecs and validate. Previously it listed only validate, suggesting that cacheAcrossSpecs was 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_EDITOR environment variable before starting Cypress. Addressed in #35208.

Dependency Updates:

  • Security

    Upgraded electron from 41.7.0 to 43.8.4 to 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 the cypress CLI, so it needs a Node.js release that includes the same fix. Addresses #35124.

  • Upgraded bundled Node.js version from 24.15.0 to 24.22.1. Addresses #35124.

  • Upgraded bundled Chromium version from 146.0.7680.216 to 150.0.7871.250. Addresses #35124.

  • Security

    Upgraded systeminformation to 5.33.18 to address the SNYK-JS-SYSTEMINFORMATION-21771271 (CVE-2026-116576) vulnerability reported in security scans. Addresses #35196.

  • Security

    Upgraded node-forge from 1.4.0 to 1.4.3 to address the Improper Certificate Validation vulnerability reported in security scans. Addressed in #35279.

  • Security

    Upgraded jimp from 0.22.12 to 1.6.1 to address an infinite loop vulnerability (CVE-2026-31808) in its file-type dependency reported in security scans. This also removes xml2js 0.4.23, which has a prototype pollution vulnerability (CVE-2023-0842). Addresses #35271.

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.