Last 12 weeks · 2 commits
2 of 6 standards met
Hi team, I am using the 2.0.1 version of @vercel/analytics package, and the vercel deployment is failing. The error details are below. package version: 2.0.1 Project framework : React (18.3.1) Error: 207: ...props.route !== void 0 && { disableAutoTrack: true }, at getRollupError (file:///vercel/path0/node_modules/rollup/dist/es/shared/parseAst.js:317:41) at error (file:///vercel/path0/node_modules/rollup/dist/es/shared/parseAst.js:313:42) at Module.error (file:///vercel/path0/node_modules/rollup/dist/es/shared/node-entry.js:17396:16) at Module.traceVariable (file:///vercel/path0/node_modules/rollup/dist/es/shared/node-entry.js:17829:29) at ModuleScope.findVariable (file:///vercel/path0/node_modules/rollup/dist/es/shared/node-entry.js:15419:39) at ReturnValueScope.findVariable (file:///vercel/path0/node_modules/rollup/dist/es/shared/node-entry.js:5684:38) at FunctionBodyScope.findVariable (file:///vercel/path0/node_modules/rollup/dist/es/shared/node-entry.js:5684:38) at Identifier.bind (file:///vercel/path0/node_modules/rollup/dist/es/shared/node-entry.js:5451:40) at CallExpression.bind (file:///vercel/path0/node_modules/rollup/dist/es/shared/node-entry.js:2833:23) at CallExpression.bind (file:///vercel/path0/node_modules/rollup/dist/es/shared/node-entry.js:12528:15) Error: Command "npm run build" exited with 1 Can someone help to look into this. Any help is appreciated.
Thought I would try the preview version of Next ( to be specific), and seems it works great, with the exception that I'm getting this error on the build-server: Would be great if [the peer dependency](https://github.com/vercel/analytics/blob/d5df714080cbfdc7ee5e84b9aa6918e291a8e979/packages/web/package.json#L127], which is now could be widened to also include preview versions. I can work around it by overriding the install command on Vercel to , but would prefer if I didn't have to do that.
What I hit Using `routepathdisableAutoTrack: truerouteroute && pathroutepathroutepathwindow.location.pathnamereact/index.test.tsx`: the route-without-path case now queues a pageview, and a both-provided regression guard. Verified fail before the fix / pass after against the real component. Closes #197.
🖖🏻 What's in there? Adds SvelteKit 3 support via while keeping on the existing SvelteKit 2 integration. Introduces a new test application for , while preserving the previous SvelteKit app as for SvelteKit 2 coverage. 🤺 How to test? Ultimate test is to use the test apps: sveltekit-old for SV2 sveltekit for SV3 Visit these apps with your devtools open on the network tab. Click on the link to navigate away. Check the payload of the POST to : you'll see the pageview attributed to the correct route. I also ran: 🔬 Notes to reviewers This mirrors the SvelteKit 3 split from vercel/speed-insights#120: use in a new export while preserving the stable SvelteKit 2 export based on .
Widen peer dependency from to and bump the dev dependency to . Vue Router 5 has no breaking changes for v4 consumers, but projects using it currently get an unmet peer warning. This resolves that while keeping v4 compatibility. Note:** The large diff is due to and playground apps using specifiers resolving to newer versions.
Why The release job authenticated to npm with . That elevated token can no longer be used (permissions revoked), so publishing is broken. This switches publishing to npm Trusted Publishing (OIDC) — the same mechanism — without adopting changesets. The workflow keeps its existing trigger () and its beta/stable split. 🤖 Generated with Claude Code
Repository: vercel/analytics. Description: Privacy-friendly, real-time traffic insights Stars: 512, Forks: 50. Primary language: TypeScript. Languages: TypeScript (80.9%), Vue (7.2%), CSS (6.5%), Astro (2.6%), JavaScript (1.9%). License: MIT. Homepage: https://vercel.com/analytics Latest release: v2.0.1 (5mo ago). Open PRs: 3, open issues: 27. Last activity: 1mo ago. Community health: 50%. Top contributors: tobiaslins, feugy, timolins, dglsparsons, chriswdmr, AndyBitz, atinux, emspishak, Ethan-Arrowood, CHC383 and others.