Skip to content

Platforms

JavaScript error monitoring for the browser

Add one script tag or install a modular npm package. Buglapse captures uncaught errors, failed requests and broken resources, and adds logs, tracing, sessions and replay when you need them.

Get startedRead the docs

All Buglapse features

JavaScript

What the browser SDK gives you

  • Errors you would not hear about

    Uncaught exceptions, unhandled promise rejections, errors inside browser API callbacks, failed HTTP requests and resources that did not load.

  • Modular by design

    Every capability is a separate integration. With the npm package you import only what you use, so the rest never reaches your bundle.

  • Or just a script tag

    The project key is already in the script URL. Integrations are switched on and off in the project settings, with no redeploy.

  • More than errors

    Logs, page-load and navigation traces, release health sessions and session replay come from the same SDK and share one context.

How it works

Install in a couple of minutes

  1. 1

    Create a project

    Sign up for free and create a project. Its DSN and the script tag are ready right away in the settings.

  2. 2

    Initialize the SDK

    Paste the script tag into the page, or install the package and call init with the project DSN.

  3. 3

    See the first issue

    Errors are grouped into issues with a readable stack trace, breadcrumbs, release and user.

main.ts

Install

echo "@buglapse:registry=https://app.buglapse.com/npm/" >> .npmrc
npm install @buglapse/browser
import { init } from '@buglapse/browser'

init({ dsn: 'https://YOUR_PROJECT_TOKEN@app.buglapse.com' })

In detail

What is captured in the browser

Integrations of the browser SDK

Global errors and promise rejections, errors thrown inside timers and event listeners, failed fetch and XHR requests, and scripts, styles or images that failed to load. Breadcrumbs record clicks, navigation, requests and console output before an error. Device and page context is added to every event, slow event handlers that block the main thread are reported, repeated identical events are deduplicated, and inbound filters drop known noise before it is sent.

Frameworks and build tools

The SDK hooks into the page itself, not into a particular library, so it works the same in a React, Vue, Svelte or Angular application and on a page with no framework at all. Errors a framework catches on its own are reported with a single call from its error handler. For readable stack traces, a bundler plugin uploads source maps from Vite, webpack, Rollup, Rspack and esbuild.

On each plan

Compare all plans
On each plan
Free Pro Team
Projects210Unlimited
Errors / month5,00025,000150,000
Replays / month101001,000

FAQ

Common questions

Still have questions?

Drop us a line — we'll help with setup, plans or self-hosting.

Contact us

or email hello@buglapse.com

Is there a separate package for my framework?
No, there is one browser SDK for every framework. It needs no framework-specific setup beyond reporting the errors your framework catches itself.
How much does it add to the page?
The npm package is modular, so you ship only the integrations you import. Session replay is the heavy one and is a separate import for that reason.
Does it work with single-page apps?
Yes. Route changes are tracked as navigation spans and breadcrumbs, and a session continues across them.

See also

Related features

Error tracking

Every error grouped into one issue with a readable stack trace, breadcrumbs, the steps to the error and the affected users.

Learn more: Error tracking

Ready to see what's happening in your app?

Create a project on the free plan and send your first event in a couple of minutes.

Create your projectRead the quickstart

Still have questions? Email hello@buglapse.com