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

my-electron-crasher

v1.0.2

Published

A minimal Electron application with BugSplat

Downloads

10

Readme

BugSplat

my-electron-crasher

The my-electron-crasher sample demonstrates how to use BugSplat's npm package to track JavaScript errors in your Electron application. This sample also demonstrates how to use Electron's Breakpad based crashReporter for tracking internal framework crashes with BugSplat. Follow these steps to get started:

  1. Clone this repository or download the zip from the releases tab
  2. Open terminal or command prompt in this project's root directory
  3. npm install && npm run start
  4. Click any of the crash buttons in the application window to test the BugSplat integration
  5. Navigate to BugSplat's AllCrash page in your web browser
  6. When prompted to log in, use the username "Fred" and password "Flintstone"
  7. Click the ID of your crash to see crash details

In order to see function names and line numbers of internal framework crashes you will need to upload symbol files to BugSplat. Symbol files are not required for JavaScript crashes.

Symbol files can be found on Electron's releases page. Use Breakpad's SymUpload utility to post symbols to BugSplat. More information about posting Breakpad symbols to BugSplat can be found here.

For more information about getting started with Electron check out the Quick Start Guide within the Electron documentation. For additional help using BugSplat, check out the documentation on our website or email support(at)bugsplat.com if you have any questions.

Good luck! © BugSplat Software Web | Twitter | Facebook