Packages

@cypress/webpack-dev-server

6.2.0 · 14 Nov 2026MIT151.9k / weekRepositoryHomepagenpmAtom feed

Upgrading @cypress/webpack-dev-server From 3.3.0 to 3.3.1

1 release in betweenevery note read

Other targets from 3.3.0Newest 3.x3.11.0Latest6.2.0
  1. 3.3.0yours
  2. 3.3.1target
0
changes to make
0
advisories fixed
0
new
5
fixes

Release by release

  1. 3.3.1

    14 Mar 20235 fixes
    • Fixed

      Fixed a bug for users running external network proxies that prevented requests from completing. Requests should now all work correctly. Fixes #4257.

    • Fixed

      Fixed a regression in 3.3.0 causing large requests such as multipart/form-data uploads to hang. Fixes #4240, #4252, and #4253.

    • Fixed

      Fixed issue where support for have.focus, not.have.focus, be.focused and not.be.focused assertions were not working. Fixes #4265.

    • Fixed

      Fixed an issue where highlighting a command's snapshot would throw an error when no application was rendered in the AUT frame. Fixes #4177.

    • Fixed

      Fix capitalization of Xvfb in error messages. Addressed in #4262.

6 other lines we could not sort, mostly version bumps
  • We've written a blog post about the 300% increase in proxy performance delivered in 3.3.0.

    3.3.1
  • Cypress no longer accidentally prints internal Electron logs when running cypress run. This bug would exhibit itself when verifying and running Cypress the first time after installation. You may have seen these logs when running in CI. Fixes #4255.

    3.3.1
  • Names given to .as() now work properly when they contain a . character. Fixes #3512.

    3.3.1
  • The proper error is now thrown when passing {log: false} to a Cypress command that failed. Fixes #3847.

    3.3.1
  • We now properly detect the branch name when running Cypress in AppVeyor. Fixed in #4234.

    3.3.1
  • We have some newly translated documentation in Chinese and Japanese. If you'd like to help in translating more, please open a pull request in our documentation repo.

    3.3.1

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.