On this page, we get you up and running with Sentry's SDK, so that it will automatically report errors and exceptions in your application.

Don't already have an account and Sentry project established? Head over to, then return to this page.


Sentry captures data by using an SDK within your application’s runtime.

# Using yarn
yarn add @sentry/browser @sentry/tracing
# Using npm
npm install --save @sentry/browser @sentry/tracing

If you're updating your Sentry SDK to the latest version, check out our migration guide to learn more about breaking changes.


Configuration should happen as early as possible in your application's lifecycle.

Once this is done, Sentry's JavaScript SDK captures all unhandled exceptions and transactions.

import * as Sentry from "@sentry/browser";
import { BrowserTracing } from "@sentry/tracing";

  dsn: "",

  // Alternatively, use `process.env.npm_package_version` for a dynamic release version
  // if your build tool supports it.
  release: "my-project-name@2.3.12",
  integrations: [new BrowserTracing()],

  // Set tracesSampleRate to 1.0 to capture 100%
  // of transactions for performance monitoring.
  // We recommend adjusting this value in production
  tracesSampleRate: 1.0,



This snippet includes an intentional error, so you can test that everything is working as soon as you set it up:


To view and resolve the recorded error, log into and open your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").