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 🙏

© 2024 – Pkg Stats / Ryan Hefner

sentry-electron-opt-out

v0.2.0

Published

A means of opting-out of error reporting from any process

Downloads

2

Readme

sentry-electron-opt-out

A means of opting-out of error reporting from any process

Automated client side error reporting is a great way to fix issues without intervention from users. Some users still insist on opting-out of this 🤷.

Example usage

Run the following code in both Electron processes:

const Sentry = require('@sentry/electron');
const { ElectronOptOut } = require('sentry-electron-opt-out');

Sentry.init({
  dsn: '__YOUR_DSN__',
  integrations: integrations => [...integrations, new ElectronOptOut()],
});

To query or change the state of error reporting, use the following code in any Electron process:

const { isEnabled, setEnabled } = require('sentry-electron-opt-out');

// Check if reporting is enabled
const reportingEnabled = await isEnabled();

// Disable error reporting
await setEnabled(false);

You can optionally pass a function which can force error reporting to be enabled. Perhaps this is a pre-requisite to using pre-release versions of you app?

// constructor(forceEnabled?: () => Promise<boolean>) {

// Example
const { app } = require('electron');

Sentry.init({
  dsn: '__YOUR_DSN__',
  integrations: integrations => [
    ...integrations,
    new ElectronOptOut(async () => {
      const version = app.getVersion();
      return version.includes('beta') || version.includes('alpha');
    }),
  ],
});