@segment/analytics-next
Analytics Next (aka Analytics 2.0) is the latest version of Segment’s JavaScript SDK - enabling you to send your data to any tool without having to learn, test, or use a new API every time.
About
Analytics Next (aka Analytics 2.0) is the latest version of Segment’s JavaScript SDK - enabling you to send your data to any tool without having to learn, test, or use a new API every time.
Live mirror of the GitHub README. Updated whenever the repo's default branch changes.
🎉 Flagship 🎉
This library is one of Segment’s most popular Flagship libraries. It is actively maintained by Segment, benefitting from new feature releases and ongoing support.
Welcome to the monorepo for Segment's latest Javascript / Typescript SDKs
analytics.js (analytics-next)
Packages
- @segment/analytics-next: Analytics.js SDK for web browsers
- @segment/analytics-node: Analytics.js SDK for Node.js
Contributing
- Contribution guidelines: CONTRIBUTING.md
- Development instructions: DEVELOPMENT.md
- Releasing (to npm): RELEASING.md
Quick facts
npm install @segment/analytics-nextHow Sourcemap Explorer detects @segment/analytics-next
We catch @segment/analytics-next from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/@segment/analytics-next/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.
- 1
Confirm the site exposes sourcemaps
In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment.
- 2
Find the package in the bundle
Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/@segment/analytics-next/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@segment/analytics-next/package.json` gives you the exact installed version.
- 3
Read the version directly from package.json
Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/@segment/analytics-next/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Recent versions
FAQ
What is @segment/analytics-next used for?
Analytics Next (aka Analytics 2.0) is the latest version of Segment’s JavaScript SDK - enabling you to send your data to any tool without having to learn, test, or use a new API every time.
How can I tell if a website is using @segment/analytics-next?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@segment/analytics-next` from two complementary signals: `node_modules/@segment/analytics-next/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.
What is the latest version of @segment/analytics-next?
1.84.0, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.
Where can I read more?
Project homepage: https://github.com/segmentio/analytics-next#readme. Source code: https://github.com/segmentio/analytics-next. Published on npm: https://www.npmjs.com/package/@segment/analytics-next. Licensed as MIT.
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for @segment/analytics-next and report the precise version. Without sourcemaps, an import / require in the page's scripts is enough to flag it.