Getting Started

Installation

Install the Reliable SDK from npm. Pick the package that matches your framework — both work the same way under the hood.

Vanilla JavaScript (any framework)#

Use @reliableapp/frontend-core for vanilla JavaScript or any non-React framework. It works in Vue, Svelte, Angular, and others today — though dedicated framework packages with idiomatic bindings are coming later. The package is published to npm under the @reliableapp scope.

bash
# npm
npm install @reliableapp/frontend-core

# pnpm
pnpm add @reliableapp/frontend-core

# yarn
yarn add @reliableapp/frontend-core

# bun
bun add @reliableapp/frontend-core

For React apps#

Use @reliableapp/react. It depends on the core package and re-exports its full API, so you only need this one install. React 18 or later is required as a peer dependency.

bash
npm install @reliableapp/react

Don't install both

@reliableapp/react already includes everything from @reliableapp/frontend-core. Installing both won't break anything, but it bloats your node_modules for no benefit.

Browser support#

Reliable supports all modern browsers — anything that ships fetch, PerformanceObserver, and ES2020. In practice that means:

  • Chrome / Edge 90+
  • Firefox 88+
  • Safari 15+
  • iOS Safari 15+

On older browsers the SDK fails silently — no thrown errors, no broken features. Newer signals like Core Web Vitals are simply skipped, but error and network capture still work.

Bundle size#

  • @reliableapp/frontend-core — ~80 KB gzipped (includes rrweb for replay)
  • @reliableapp/react — ~3 KB gzipped (core marked as external)

Replay (rrweb) accounts for the bulk of the core size. If you don't need session replay, set captureReplay: false in your config — the rrweb code is still in the bundle (since it's bundled in), but it won't run or send any data.

What's next

Head to the Quick Start to see the SDK in action with a working example.

Going to production?

Add source maps to your build pipeline so production stack traces resolve to real file/line/function names. One line in your build script + one CI env var. Don't skip this if you care about debugging prod errors.