@amplitude/analytics-browser
Official Amplitude SDK for Web
About
Official Amplitude SDK for Web
What detecting @amplitude/analytics-browser tells you about a site
This is Amplitude's modern browser SDK, and its presence marks a product that tracks user events for behavioural analytics, retention and funnel analysis at a fairly serious scale. Amplitude is an enterprise-leaning choice, so finding it often points to a larger or growth-focused organisation with a real analytics team behind it. The analytics-browser namespace specifically is the newer unified SDK that replaced the older amplitude-js, so its presence also dates the integration as relatively modern. It reveals a company that invests in understanding cohorts and conversion rather than treating analytics as a bolt-on.
Why the exact @amplitude/analytics-browser version matters
The @amplitude/analytics-browser line is itself the successor to the legacy amplitude-js package, so seeing it at all signals a post-migration setup. Within it, majors changed plugin architecture, autocapture behaviour and session handling, so the exact version tells you which instrumentation model and which default-capture settings the site relies on.
@amplitude/analytics-browser in a real-world stack
When you find @amplitude/analytics-browser in a bundle, it rarely travels alone. Amplitude plugins for session replay or autocapture, and sometimes a separate experimentation SDK.
Quick facts
npm install @amplitude/analytics-browserWhat @amplitude/analytics-browser pulls in
@amplitude/analytics-browser declares 9 direct dependencies — each one also rides into any bundle that ships @amplitude/analytics-browser, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .
How Sourcemap Explorer detects @amplitude/analytics-browser
@amplitude/analytics-browser ships as v2.45.5, published 2026-07-28 and carries 9 direct dependencies, 328 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when @amplitude/analytics-browser rides inside a deployed bundle — here is how the detection works.
We catch @amplitude/analytics-browser from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/@amplitude/analytics-browser/ 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 — that map is where the `@amplitude/analytics-browser` paths live.
- 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/@amplitude/analytics-browser/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@amplitude/analytics-browser/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/@amplitude/analytics-browser/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Major releases of @amplitude/analytics-browser
When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the @amplitude/analytics-browser version a site actually ships against the ecosystem.
Recent versions
@amplitude/analytics-browser README
Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.
Amplitude-TypeScript
This is Amplitude's latest version of the JavaScript SDK, written in TypeScript.
Development
If you plan on contributing to this SDK, here's how you can start.
- Clone GitHub repo
- Install dependencies
- Build and link packages
$ git clone git@github.com:amplitude/Amplitude-TypeScript.git
$ nvm use
$ pnpm --version
$ pnpm install
$ pnpm build
Check our guidelines for repo contributions on CONTRIBUTING.md.
Projects
- Amplitude SDK for Web
- Amplitude SDK for Node.js
- Amplitude SDK for React Native
Testing Locally
To test the SDK locally, you can run our test server.
Before running the test server for the first time, copy ".env.example" as ".env" and replace the variables in '.env' with your own variables.
Run pnpm dev to run the test server. It will open up to the home page automatically in your default browser.
For more details visit the Test Server README.md
Troubleshooting
If you ever see an error that looks like this while running an Nx command (pnpm test, pnpm build, etc...):
Lerna (powered by Nx) DB transaction operation error: SqliteFailure(Error { code: SystemIoFailure, extended_code: 522 }, Some("disk I/O error"))
Run npx nx reset and try again
Documentation
See our Typescript SDK Reference for a list and description of all available SDK methods.
FAQ
What is @amplitude/analytics-browser used for?
Official Amplitude SDK for Web
How can I tell if a website is using @amplitude/analytics-browser?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@amplitude/analytics-browser` from two complementary signals: `node_modules/@amplitude/analytics-browser/` 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.
How do I find out which version of @amplitude/analytics-browser a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `@amplitude/analytics-browser/package.json` carries the exact `version` string — Sourcemap Explorer extracts it in one click on the Stack tab, and you can do it by hand in DevTools by opening the `.map` file and searching for `node_modules/@amplitude/analytics-browser/package.json`. That is far more reliable than inferring the version from an asset-hash or a `?ver=` query string, which is all surface-level detectors have to go on. The current npm release is 2.45.5, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.
What is the latest version of @amplitude/analytics-browser?
2.45.5, 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.
Is @amplitude/analytics-browser actively maintained?
Very actively maintained — the last release shipped within the past three months. The last published release was 2026-07-28. Source code: https://github.com/amplitude/Amplitude-TypeScript.
Where can I read more?
Project homepage: https://github.com/amplitude/Amplitude-TypeScript. Source code: https://github.com/amplitude/Amplitude-TypeScript. Published on npm: https://www.npmjs.com/package/@amplitude/analytics-browser. Licensed as MIT.
Keep reading on Sourcemap Explorer
Practical guides
Alternative tools
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for @amplitude/analytics-browser and report the precise version (the registry's latest is v2.45.5, published 2026-07-28; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.