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

nightmare-crash-reporter

v0.1.0

Published

Adds a crash reporter to NightmareJS

Downloads

9

Readme

nightmare-crash-reporter

Add Electron crash reporting to your Nightmare scripts.

Usage

Require the library: and pass the Nightmare library as a reference to attach the plugin actions:

var Nightmare = require('nightmare');
require('nightmare-crash-reporter')(Nightmare);

When started, nightmare-crash-reporter will scan for an open port on localhost starting with 3000, then stand up a temporary crash report server to accept crash reports. When Nightmare is ended (either gracefully or via a crash), the temporary crash report server will be stopped and the port freed.

.crashReporter([options])

Start the crash reporter with the given options. If no options are given, the crash reporter will not be started unless the DEBUG environment variable is set. The options provided are ultimately passed to the crash reporter; all of the options available to the crash reporter are available to the options hash. This method resolves to the port the temporary crash report server is started on.

omitDump

Remove the temporary dump after the crash is reported.

companyName (defaults to 'Nightmare')

Mandatory from Electron's crash reporter. Use this to denote who is doing the crash reporting.

productName

From Electron's crash reporter. Use this to denote what is doing the crash reporting.

dumpDirectory (defaults to /tmp)

The target directory for crash report dumps.

callback

If a crash occurs, this function will get called with an error (if there was a problem moving the dump if using options.dumpDirectory) and the fields from the original crash report. The saved path of the dump is included on the fields hash.

Example

var Nightmare = require('nightmare');
require('nightmare-crash-reporter')(Nightmare);
var nightmare = Nightmare();
nightmare
  .crashReporter({
    dumpDirectory: '/some/path',
    callback: function(err, fields){
      console.dir(fields);    
    })
  .someActionThatCausesCrash()
  .end()
  .then(()=>console.log('done'));