npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@flareapp/electron

v2.6.0

Published

Electron SDK for flareapp.io

Readme

@flareapp/electron

Electron SDK for Flare error tracking. It captures JavaScript errors in both Electron processes and routes every report through the main process, so your API key lives in exactly one place.

What it captures

  • Main process: uncaught exceptions and unhandled promise rejections.
  • Renderer process: window.onerror and unhandledrejection, plus anything you report manually.
  • Process crashes: render-process-gone and child-process-gone, reported with the crash reason and exitCode.

It does not capture native crashes (C++/Crashpad minidumps). Only JavaScript-level errors are sent to Flare.

Installation

npm install @flareapp/electron

electron is a peer dependency; this package expects your app to provide it.

Quick start

Flare needs wiring in all three Electron contexts. The API key is configured once, in the main process.

// main.ts
import { flare } from '@flareapp/electron/main';

flare.light('YOUR_FLARE_API_KEY');
// preload.ts — required so renderer reports reach main over contextBridge
import { exposeFlare } from '@flareapp/electron/preload';

exposeFlare();
// renderer entry, e.g. main.tsx / index.ts — installs the global listeners
import '@flareapp/electron/renderer';

Point your BrowserWindow at the preload script with contextIsolation: true (the default).

Using a UI framework

When your renderer uses React, Vue, or Svelte, inject the Electron Flare instance through the framework's /inject entry instead of the @flareapp/js web singleton. See the framework configuration guides:

Identifying users

Set the user in the main process; it is stamped on main-origin reports and on forwarded renderer reports:

import { flare } from '@flareapp/electron/main';

flare.setUser({ id: 123, email: '[email protected]', fullName: 'Jane Doe' });

Recognised fields: id, email, fullName, ipAddress; extra keys land in user.attributes. Pass null to clear. The main-process user is authoritative for forwarded renderer reports.

Documentation

Full documentation on the report flow, beforeSubmit filtering, sender trust, attaching users, and the framework integrations is available at flareapp.io/docs/javascript/electron/how-it-works.

License

The MIT License (MIT). Please see License File for more information.