Introduction
The Flare JavaScript client runs in the browser. It catches unhandled errors and unhandled promise rejections and sends them to Flare with a stack trace and browser context. It can also send structured logs, trace page loads and navigations, and, in the framework packages, time how long your components take to mount.
What you get
- Error tracking. Unhandled errors are caught and reported automatically, with the original source code in the stack trace once you add sourcemaps. See reporting errors.
- Structured logs. Send log messages with levels and attributes, batched and flushed for you. See the logs introduction.
- Tracing. Page loads, navigations, and outgoing requests become spans you can inspect in a waterfall view. See how tracing works.
- Component profiling. Framework packages can time how long a component takes to mount. See how component profiling works.
Browser and backend errors
You can send browser errors and Laravel backend errors to the same Flare project to keep them together. Configure both clients with that project's key. Use separate projects when you want separate error lists or different notification recipients, and group related projects together for easier navigation.
See organizing projects and project notification settings to choose the setup that fits your team.
Pick your framework
Every framework package builds on the core browser client, so start with the guide for the framework you use:
No framework, or a plain JavaScript project? Continue with the quick start.
On this page