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-cli-deploy-bugsnag

v0.2.0

Published

An ember-cli-deploy plugin to upload sourcemaps to Bugsnag.

Downloads

1,929

Readme

ember-cli-deploy-bugsnag

NPM release Build Ember Observer

An Ember CLI Deploy plugin for uploading sourcemaps to Bugsnag.

To send errors to Bugsnag, see ember-cli-bugsnag.

Installation

  • ember install ember-cli-deploy ember-cli-deploy-build ember-cli-deploy-bugsnag

Quick start

Enable sourcemaps for all environments in ember-cli-build.js:

/* jshint node:true */
/* global require, module */
var EmberApp = require('ember-cli/lib/broccoli/ember-app');

module.exports = function(defaults) {
  var app = new EmberApp(defaults, {
    // …
    sourcemaps: {
      enabled: true, // This allows sourcemaps to be generated in all environments
      extensions: ['js']
    }
  });

Set Bugsnag options in your config/deploy.js. The following example assumes the values for the options will be set as environment variables on your server.

  /* jshint node: true */

  module.exports = function(deployTarget) {
    // …

    ENV['bugsnag'] = {
      apiKey: process.env.BUGSNAG_KEY,
      publicUrl: process.env.BUGSNAG_PUBLIC_URL,
    };

    // …

    return ENV;
  };

Config Options

ember-cli-deploy-bugsnag options

Set in config/deploy.js:

| Name | Type | Required | Default | Description | ---------- | ------------- | -------- | -------- | --------- | | apiKey | string | Yes | <none> | Your Bugsnag Notifier API key. | | distFiles | array of strings | No | context.distFiles | The array of built project files. This option should be relative to distDir. By default, this option will use the distFiles property of the deployment context. | | overwrite | string | No | true | If set to false, existing sourcemaps for the same version of your app will not be overwritten. Options are true or false. | | publicUrl | string | Yes | <none> | The fully qualified domain name for your application e.g., https://app.fancy-app.com | | includeAppVersion | boolean | No | true | Whether to tag the uploaded sourcemaps as belonging to a particular app version. |

Related plugin options

Set by other Ember CLI Deploy plugins:

| Name | Type | Default | Description | Plugin | | ---------- | ------------- | -------- | ----------- | ------ | | distDir | string | tmp/deploy-dist | The path to your app's distribution directory. | ember-cli-build | | revisionKey | string | <none> | The unique identifier of a build based on its git tag. | ember-cli-deploy-revision-data | | gzippedFiles | array | <none> | A list of files that have been gzipped in the build. | ember-cli-deploy-gzip |

Deploying to Heroku

Add Heroku's Ember buildpack:

  heroku buildpacks:set https://codon-buildpacks.s3.amazonaws.com/buildpacks/heroku/emberjs.tgz

Heroku strips away git information, so this addon grabs the revision info from the SOURCE_VERSION environment variable Heroku provides. Then you need to add the following to config/environment.js:

  /* jshint node: true */
  module.exports = function(environment) {
    // …
    if (environment === 'production') {
      // …
      ENV.currentRevision = process.env.SOURCE_VERSION;
      // …
    }
    // …
    return ENV;
  };

Developing

Running

Running Tests

  • npm test (Runs ember try:each to test your addon against multiple Ember versions)
  • ember test
  • ember test --server