@vercel/analytics
2.0.1 · 12 Mar 2026MIT10.8M / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/analytics From 1.0.1 to 2.0.1
19 releases in betweennotes for 18
Reading releases, release notes and advisories…
- 2+
- changes to make
- 0
- advisories fixed
- 8+
- new
- 10+
- fixes
Counted from 18 of 19 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking2.0.0
- Breaking2.0.0
Release by release
- Fixed
nuxt: Set nuxt as optional dependency
- Fixed
- 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 - New
feat: load dynamic configuration(#184) — analytics config can now be loaded dynamically - Fixed
fix: src and endpoint paths do not work when relative
- Breaking
- Fixed
nuxt: Remove the module as breaking change
- Fixed
- New
nuxt: Add support for
injectAnalytics()and Nuxt module - New
Add
undefinedto AllowedPropertyValues type
- New
- New
Support configurable deployment basepath
- Fixed
next/jest does not support import.meta
- New
- Fixed
#157: Error when rendering Nuxt component
- Fixed
- New
Route support for Astro, Nuxt, Remix, Sveltekit and Vue
- New
next/remix/react supports updating beforeSend
- New
1.3.2nothing new or fixed in the note
4 other lines we could not sort, mostly version bumps
- 1.3.2
React 19 support
- 1.1.4
server/track: Always consume the response body for a track request
- 1.1.3
Server events can now be sent when deployment protection is enabled
- 1.1.1
Upgrade @vercel/style-guide
5 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.