Packages

@cypress/vue

7.0.1 · 28 Sep 2026MIT50.3k / weekRepositoryHomepagenpmAtom feed

Your version

Where each line stands

Plan an upgrade
  • 7.x7.0.1No known advisoryLatest line
  • 6.x6.0.3No known advisoryTo 7.0.1
  • 5.x5.0.5No known advisoryTo 7.0.1
  • 4.x4.2.2No known advisoryTo 7.0.1
  • 3.x3.1.2No known advisoryTo 7.0.1
  • 2.x2.2.4No known advisoryTo 7.0.1

Latest releases

All 35 releases
  1. 7.x · latest line
  2. 7.0.1

    28 Sep 2026
    • Fixed a regression in 7.0.0 that caused the test runner not to check for updates. Fixes #15829.

    • The component testing spec list search input no longer throws an exception when hitting Enter. Addressed in #15833.

    • The preferred file opener modal no longer appears behind the command log. Addressed in #15831.

  3. 7.0.0

    26 Aug 2026
    • Breaking

      Installing Cypress on your system now requires Node.js 12+. Addresses #9545.

    • We introduced several breaking changes to cy.intercept(). See the cy.intercept() docs for full usage examples. Breaking changes:

    • Component tests have been migrated to use a dedicated test runner and are bundled differently. See the Migration Guide for full examples on how to migrate. Addressed in #14479.

  4. 6.x · maintenance
  5. 6.0.3

    13 Apr 2026

Notes older than 90 days are read on the Releases tab.

Dependency tracking

Know when your own dependencies move

@cypress/vue shipped a new major in the last 12 months, among 3 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.

How dependency tracking works

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.