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

node-crashlytics

v0.0.4

Published

An unofficial client for the Crashlytics API

Downloads

12

Readme

Usage

var Crashlytics = require('crashlytics');
var api = new Crashlytics(
	'[email protected]',   // email of the account you're logging into
	'superSECURE_pa$$w0rd', // password for that same account
	'0123456789abcdef01...' // developer token (see below)
);

// set up your session
api.login(function(err, api) {
	if (!err) {
		var now = ~~(+new Date()/1000);
		var options = {
			end   : now,
			start : now - 2592000
		};

		// get the last 30 days worth of error events for your awesome app
		api.events('ca.company.awesomeapp', options, function(err, events) {
			// do something useful with your event counts!
			processMetricsEvents(events);
		});
	}
});

Methods

  • crashlytics.builds(app, callback)

    Gets the list of all builds known to Crashlytics and the associated info.

  • crashlytics.issues(app, [options], callback)

    Gets a list of according to the supplied options.

  • crashlytics.events(app, [options], callback)

    Gets a list of timestamped event counts for all error events (useful for graphing).

Developer Tokens

The developer token supplied as the 3rd argument to the constructor can be retrieved from the Crashlytics web app. If you snoop on your web traffic (the Chrome debugger's network tab is very useful for this) you will see the X-CRASHLYTICS-DEVELOPER-TOKEN header being sent after you have logged in. This will be a 160-bit hex number. Just copy this and use it in your code.