Packages

@vercel/analytics

2.0.1 · 12 Mar 2026MIT10.8M / weekRepositoryHomepagenpmAtom feed

Your version

Where each line stands

Plan an upgrade
  • 2.x2.0.1No known advisoryLatest line
  • 1.x1.6.1No known advisoryTo 2.0.1
  • 0.x0.1.11No known advisoryTo 2.0.1

Latest releases

All 40 releases
  1. 2.x · latest line
  2. 2.0.1

    12 Mar 2026
    • nuxt: Set nuxt as optional dependency

  3. 2.0.0

    10 Mar 2026
    • Breaking

      License changed from MPL-2.0 to MIT

    • Breaking

      Nuxt: introduce module support. If you need to configure it, load injectAnalytics() from @vercel/analytics/nuxt/runtime

    • feat: load dynamic configuration (#184) — analytics config can now be loaded dynamically

  4. 1.x · maintenance
  5. 1.6.1

    2 Dec 2025
    • nuxt: Remove the module as breaking change

Dependency tracking

Know when your own dependencies move

@vercel/analytics shipped a new major in the last 12 months, among 4 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 19 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.