Packages

@nuxt/telemetry

2.9.1 · 31 Aug 2026MIT3.4M / weekRepositoryHomepagenpmAtom feed

Upgrading @nuxt/telemetry From 0.0.13 to 2.9.1

56 releases in betweennotes for 19

Other targets from 0.0.13Newest 0.x0.0.14
1.0.0 has no release note on GitHub or in the repository's changelog, so its breaking changes are missing from the counts below.
  1. 0.0.13yours
  2. 1 release
  3. 1.0.0major
  4. 21 releases
  5. 2.0.0major
  6. 31 releases
  7. 2.9.1target
1+
change to make
0
advisories fixed
12+
new
17+
fixes

Counted from 19 of 56 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking2.0.0

Release by release

  1. 2.9.1

    31 Aug 20261 new · 8 fixes
    • New

      Respect DO_NOT_TRACK env var

    • Fixed

      Include status code in failed telemetry request error

    • Fixed

      Abort telemetry request after 5s

    • Fixed

      Lowercase os type independently of locale

  2. 2.8.0

    31 Mar 20262 new
    • New

      Detect if nuxt is run by an agent

    • New

      Detect nitro preset

  3. 2.7.0

    7 Feb 20262 new · 1 fix
    • New

      Replace unneeded dependencies

    • New

      Move nuxt/kit to peer deps

    • Fixed

      Support nuxt v4 flags

  4. 2.6.6

    18 Mar 20251 fix
    • Fixed

      Remove dependency on parse-git-config

  5. 2.6.5

    11 Feb 20251 fix
    • Fixed

      Expand allowed engines.node

  6. 2.6.4

    6 Jan 20251 fix
  7. 2.6.3

    6 Jan 20251 fix
    • Fixed

      cli: Expose main and run it from bin

  8. 2.6.2nothing new or fixed in the note

51 internal lines (docs, tests, tooling) left out.

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.