Packages

@cypress/webpack-batteries-included-preprocessor

5.0.0 · 26 Aug 2026MIT154.9k / weekRepositoryHomepagenpmAtom feed

Your version

52 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.

  1. 5.x · latest line
  2. 5.0.0

    26 Aug 2026
    • Deprecated

      The cypress-plugin-retries plugin 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.

  3. 4.x
  4. 4.2.0

    15 Jul 2026
    • Videos can now be recorded when running Electron in --headed mode. Addresses #1767.

    • cypress cache list now prints the last time the cached binary was accessed for each version present. Addresses #6682.

    • We fixed a regression in 3.8.3 where HTTPS requests could experience slowdown. Fixes #6659.

  5. 4.1.1

    9 May 2026
  6. 4.1.0

    13 Apr 2026
    • There is a new cypress info command to see the locally detected browsers and other information related to Cypress. Addresses #4540.

    • You can now click a 'Try Again' button to recheck if the server at the designated baseUrl is running within the warning message during cypress open. Addresses #3284.

    • The plugins file function's config argument now includes projectRoot (absolute path to the root of the project) and configFile (absolute path to the configuration file). Addresses #5941.

  7. 4.0.3 – 4.0.42 releases without a noteShow each
  8. 4.0.2

    27 Aug 2025
    • Fixed a bug where Firefox tests could fail to run on macOS if another instance of Firefox was open. Addresses #6380.

    • Updated @cypress/browserify-preprocessor to 2.1.4, fixing a regression involving non-top-level require()s in tests. Addresses #6403.

    • Fixed a bug where re-running a failed workflow in GitHub Actions would not generate a new Dashboard run. Addresses #6450.

  9. 4.0.1

    19 Aug 2025
    • Fixed a bug where Chromium could not be detected on macOS. Addresses #6358.

    • Fixed bugs where Edge and Firefox Nightly could not be detected on macOS. Addresses #6354 and #6345.

    • Fixed a bug where 64-bit editions of Firefox could not be detected on Windows. Addresses #6355.

  10. 4.0.0

    8 Aug 2025
    • Breaking

      The --browser flag no longer accepts canary as its sole argument to run Chrome Canary. You now have to specify chrome:canary to use the Chrome Canary browser. Addresses #6243.

    • Breaking

      Installing Cypress on your system now requires Node.js 8+. Addresses #5632.

    • Mocha, Chai, and Sinon.JS has been upgraded which includes a number of breaking changes and new features. Addresses #2528, #2529, #2866.

  11. 3.x
  12. 3.1.2

    24 Jul 2025
    • Fixed a regression caused in 3.1.1 where we attempted to set a property on an invalid cookie sent from a server. Fixes #2724.

    • Fixed Cypress not correctly aborting long running connections (such as server sent events) on proxied requests. Fixes #2612.

    • Fixed bug where tests were failing due to assertions causing Cypress to accidentally iterate through cross origin iframes. If you were seeing "random" cross origin errors, this likely fixes those issues. Fixes #2784.

  13. 3.1.1

    1 Jul 2025
    • Infinite .Trash-0 folder on Ubuntu 16

    • Setting HTTPS cookies in certain situations

    • You can now pass a flag option to cy.writeFile(). The following flags are available. Fixes #1249.

  14. 3.1.0

    13 May 2025
    • Cypress can now run tests in parallel across multiple virtual machines, or can be parallelized on a single machine. Cypress will automatically figure out, detect, and load balance all of your specs in the fastest and most efficient way possible. There is no configuration other than passing a --parallel flag and spinning up multiple machines on your CI provider. From our experiments you can expect to see approximately 40% reduction in overall run time per machine you add. However, attempting to run in parallel on a single machine requires server grade hardware with dozens (or even hundreds) of CPU's and GB of RAM to run efficiently. A much better and simpler approach is to use a cluster of docker containers that are all isolated from each other. Any standard CI service (CircleCI, TravisCI, etc) comes with the ability to do this. We automatically tap into their environment variables to make parallelization possible without you having to configure anything.

    • Beyond parallelization, you now have the ability to group multiple runs with each other so that they show up together (grouped) in the Dashboard. This enables you to test different applications, groups of specs, or different environments (like development, staging, production) and see all of the results together. We know how important cross browser testing is to everyone, so we built this to lead directly into aggregating the results of multiple browsers into a single run.

    • The Dashboard Service has been updated to show you more visual information about what happened during a run. You can see how specs were parallelized and you can calculate the effect of adding or removing machines to help reduce the overall run time.

  15. 3.0.4 – 3.0.74 releases without a noteShow each
  16. 3.0.3

    7 Jun 2024
    • Reverted the Chrome argument that disabled RootLayerScrolling which was used to prevent the application under test from "shaking" due to a bug in versions 66 and 67. This workaround inadvertently created a different and much more severe bug in Chrome 68 that would miscalculate pointer coordinates. This led to Cypress giving confusing errors about elements being covered up on action. This is still a bug in Chrome, and is fixed in Canary but has not yet been released to the stable Chrome 68 channel. Nevertheless, removing the RootLayerScrolling flag does fix it. We did several experiments to try to ensure that the "shaking" behavior does not exhibit itself in Chrome 68. We have limited the --disable-blink-features=RootLayerScrolling flag to Chrome 66 and Chrome 67. Fixes #2223 and #2215 and #2037.

    • Fixed another bug with Chrome that caused the chromeWebSecurity: false option to not be respected. This was due to Chrome progressively rolling out trials of a new option that attempts to isolate sites (and iframes) in their own child process if their origins are different. Fixes #1951 and #2001 and #715.

    • Fixed Cypress hanging in CI due to excessive and unnecessary globbing. We finally tracked down this issue which made it appear as if Cypress was "hanging" after closing a spec file and then attempting to open the next one. Fixes #2183 and #1905 and #1912.

  17. 3.0.2

    31 Aug 2023
    • Screenshots taken with cy.screenshot() on 2x DPI are now taken at the correct full size. Fixes #1857 and #2018.

    • Windows users no longer exit with EPIPE errors when running cypress run in newer versions of node. Fixes #1841 and #2044.

    • Fixed issue where applications programmatically stealing focus would lead to slow runs in Electron when running via cypress run. #1909 and #1892.

  18. 3.0.1

    29 Aug 2023
    • Seeded KitchenSink tests no longer fail. Fixes #1812.

    • The binary cache now correctly works and will not reinstall Cypress if an existing version is already installed. Fixes #1813.

    • Closing the Electron browser and then opening Chrome no longer causes cy.screenshot() to fail. Fixes #1820.

  19. 3.0.0

    14 Aug 2023
    • Removed

      screenshotOnHeadlessFailure has been removed as an option in cypress.json. Instead you can now control this behavior directly with code by setting screenshotOnRunFailure to false within the new Screenshot API. Fixes #1140 and #1754.

    • There is a new cy.task() command that enables you to go outside the browser to perform tasks directly in node. This will make it easy to setup, scaffold, seed, talk to your database, or anything else useful on a backend.

    • cy.screenshot() has been rewritten from the ground up. It now takes a screenshot of only the application under test by default. It also can take full page screenshots or element only screenshots. This is the first step of Cypress Dashboard support for screenshot diffing.

  20. 2.x
  21. 2.1.1 – 2.4.113 releases without a noteShow each
  22. 2.1.0

    24 Aug 2020
    • Prevent a bug with node-sass on OSX + Windows when local node version does not match bundled node when importing components directly in spec files. The underlying issue was because we forgot to update Buildkite and Appveyor when we upgraded Electron in 2.0.0. Fixes #1387 and #1390.

    • The Selector Playground has been updated to automatically prefer data-cy, data-test or data-testid attributes when providing the unique selector for an element. Additionally it now exposes a public API that you can use to control how it determines which selector to use. Fixes #1135.

  23. 2.0.1

    13 Aug 2020
    • Using cy.contains() with a regexp argument is now properly escaped. Fixes #1322.

    • Fixed a runaway regexp causing large .js files to take dozens of seconds to process. This was a regression caused by 2.0.0 with the new modifyObstructiveCode option. We've optimized the regexp and the performance is back to being almost identical to transparently passing responses through. Fixes #1330.

  24. 2.0.0

    10 Aug 2020
    • Removed

      Removed the flag --disable-background-networking from the Chrome launch args to fix problems in CI that would throttle XHR callbacks by up to 20-30 seconds. Fixes #1320.

    • The built in default Electron browser has been bumped from version 53 to 59. This version represents the version of Chromium that Electron is using. In other words, running cypress run (or via Electron) will be like running your tests in Chrome 59 now. Although it is unlikely this would actually break any of your tests - it is technically possible they could behave differently. Fixes #895 and #891 and #823 and #860 and #1011 and #1252 and #1276.

    • We are now detecting and automatically stripping code that obstructs Cypress from being able to test your application. Specifically, we are removing JavaScript code that tries to prevent clickjacking and framebusting. We have written very conservative rules that do their best to only strip these specific JS snippets, but it is technically possible that it may unintentionally rewrite valid JS if they match the regexp patterns. There is a new configuration option called modifyObstructiveCode that is true by default. If you are experiencing problems after upgrading, you can turn this off and this will disable modifying your JS code. If you were using Cypress and upon visiting your website you would experience seemingly "random" redirects - these problems should now be eliminated. Fixes #886 and #1245 and #1064 and #992 and #692 and #352.

  25. 1.x
  26. 1.3.3

    10 Aug 2020
  27. 1.3.2

    3 Aug 2020

    Reading the note…

  28. 1.3.1

    23 Jul 2020

    Reading the note…

  29. 1.3.0

    23 Jul 2020
    • Plugins now emit a before:browser:launch event exposing you the browser that will be launched and its launch arguments. This enables you to modify the arguments prior to launching the browser. You can also use these arguments to modify how Chrome runs and to also test Chrome extensions. Fixes #691 and #298.

    • We have launched a "CSS Selector Playground", a new UI button in the Test Runner that enables you to highlight elements in your application and receive a unique selector. You can also find elements by their text content. These mimics cy.get() and cy.contains() behavior. Additionally you can copy the generated Cypress command to your clipboard or output the generated selector to your console. This feature is in beta. It only works in Chrome (not in Electron). We are aware of some bugs in it, but it is good enough for use and feedback. Please check out issue #917, watch an animated gif demonstration, and leave any feedback you have there. Fixes #917.

  30. 1.2.0

    21 Jul 2020
    • Plugins can now return a Promise and modify the yielded config to set new configuration values and environment variables. Fixes #1042 and #909 and #576.

    • There is a new userAgent option in cypress.json. This enables you to change the userAgent of the browser for the entire browsing session. Fixes #364.

    • There is a new blacklistHosts option in cypress.json that allows you to block requests made to those hosts. Blocked requests will respond with a 503 status code. This is useful for blocking 3rd party domains like Google Analytics. We have added a new recipe demonstrating this. Fixes #442.

  31. 1.1.4

    20 Jul 2020

    Reading the note…

  32. 1.1.3

    20 Jul 2020
    • JSON fixtures with unicode escape sequences are now parsed correctly. Fixes #964.

    • The default browserify plugin no longer fires watched:file:changed twice leading to an uncaught exception that was popping up in the console. Also fixed a minor state bug in the browserify package. Fixes #968.

    • Cypress no longer reports Electron as the browser that ran in the Dashboard Service when a different browser was run. Fixes #854.

  33. 1.1.2

    20 Jul 2020
    • Fixed a regression caused by .type() adhering to maxlength incorrectly. Special character sequences were not respected. Now .type() works with special characters and implements a complete fix for maxlength. In addition to it working, it now fires all applicable browser events without modifying the actual input value. Fixes #955.

    • Errors coming from plugins now display correctly in the Test Runner. Fixes #945.

  34. 1.1.1

    17 Jul 2020
    • Fixed a bug swallowing plugin errors due to undefined reject function. Fixes #934.

    • .type() now respects the maxlength attribute and will not type beyond it. Fixes #928.

  35. 1.1.0

    16 Jul 2020

    Reading the note…

  36. 1.0.5

    16 Jul 2020

    Reading the note…

  37. 1.0.4

    15 Jul 2020

    Reading the note…

  38. 1.0.3

    15 Jul 2020

    Reading the note…

  39. 1.0.2

    15 Jul 2020

    Reading the note…

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.