@cypress/schematic
6.0.0 · 26 Aug 2026MIT116k / weekRepositoryHomepagenpmAtom feed
Upgrading @cypress/schematic From 1.7.0 to 2.0.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 1
- change to make
- 0
- advisories fixed
- 0
- new
- 1
- fix
Before you upgrade
Tick each one off as you go- Breaking2.0.0
Release by release
- Breaking
Removed the flag
--disable-background-networkingfrom the Chrome launch args to fix problems in CI that would throttle XHR callbacks by up to 20-30 seconds. Fixes #1320. - Fixed
- Breaking
14 other lines we could not sort, mostly version bumps
- 2.0.0
The built in default
Electronbrowser has been bumped from version53to59. This version represents the version ofChromiumthat Electron is using. In other words, runningcypress run(or viaElectron) will be like running your tests inChrome 59now. 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. - 2.0.0
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
modifyObstructiveCodethat istrueby 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. - 2.0.0
We are now clearing the browser's disk cache each time it opens (before any tests run). This means that any files that have been cached from
Cache-Controlheaders will be cleaned and removed. In the future, we will expose a newcy.clearCache()method to provide finer grained control of clearing the cache on a per test basis. But for now, this is an improvement. Fixes #1124. - 2.0.0
The
--specoption is now normalized against the current working directorycwdinstead of the project that you are running Cypress in. That means passing a path from the command line to a spec file will now work even when the project path is notcwd. Fixes #1159. - 2.0.0
blacklistHostswould occasionally not work if you were blacklisting a host that had previously cached a file. In this case, the browser would serve it from disk and not make an actual HTTP request. This issue has been solved by clearing the cache when the browser opens. Fixes #1154. - 2.0.0
blacklistHostsis now correctly accepted via the--configCLI flag. - 2.0.0
- 2.0.0
Basic auth is working again in Chrome 63 and Chrome 64. We "for real" fixed it this time by adding auth headers automatically at the network proxy layer and bypassed the browser altogether. We automatically apply auth headers if you provide a username/password in the URL of a
cy.visit(url). We also added a newauthoption to specify theusername/passwordusingcy.visit(url, options). All of the requests that match the origin of theurlwill have theAuthorization: Basic <...>headers added. Fixes #1288. - 2.0.0
We now properly display nested objects and arrays that come from
cypress.jsonin the Settings tab in the Desktop Application. - 2.0.0
There's now a proper "empty view" when you go to setup your project to record on our Dashboard and you have not created any Organizations. Fixes #1306.
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.