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

ember-error-tracker

v1.2.6

Published

Error handling and logging addon for Ember.js.

Downloads

18

Readme

Ember Error Tracker

NPM

Build Status Maintainability license-badge

ember-error-tracker enables the handling and logging of uncaught errors. The error is logged along with a specified number of events that led to it and can be consumed either by the console or a custom api endpoint.

Compatibility

  • Ember.js v2.18 or above
  • Ember CLI v2.13 or above

Installation

ember install ember-error-tracker

Getting started

Add the configuration to your config/environment.js.

Example:

'ember-error-tracker': {
  maxLogStackSize: 10, // the number of events to track
  listeners: {
    ember: {
      rsvp: true,
      ember: true,
      actions: true,
    },
    window: true,
  },
  events: ['click', 'input', 'scroll'], // you can add any js events
  consumers: {
    console: true,
    api: { // set to false if you just want to use it locally
      endPoint: 'http://your.api/log'
      key: 'SUPERSECRETKEY'
    },
  }
}

Enable babel source-maps in your ember-cli-build.js if you want to find out the original position of the error.

You might only want to enable this in production since it affects building time and can slow down your hot reload times.

'use strict';

const EmberApp = require('ember-cli/lib/broccoli/ember-app');

module.exports = function (defaults) {
  let app = new EmberApp(defaults, {
    babel: {
      sourceMaps: 'inline'
    },
    sourcemaps: {
      enabled: true,
      extensions: ['js']
    }
  });
}

API endpoint payload

The payload that is sent to your custom API endpoint will look like this (depending on your configuration).

const payload = 
{
  error: {
    source: String, // error source e.g.: 'ember', 'window' etc.
    timestamp: Number,
    error: {
      message: String,
      stack: String // stracktrace that can be parsed (https://www.npmjs.com/package/stacktrace-parser)
    }
  },
  events: [{
    type: String,
    timestamp: Number,
    location: String, // the path on which the error occured e.g.: '/'
    target: {
      selector: String,
      text: String // the text inside the selector
    }
  }],
  userAgent: String, // can be parsed (https://www.npmjs.com/package/bowser)
  screen: {
    resolution: {
      width: Number,
      height: Number
    },
    viewPort: {
      width: Number,
      height: Number.
    }
  }
}

Source maps to find original error position

To get the original position of the error in the source code you can use mozilla/source-maps. The location of the source map in a production build can be found at the end of the minified js file.

Contributing

See the Contributing guide for details.

License

This project is licensed under the MIT License.