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

grunt-raygun-deployment

v1.1.1

Published

Grunt plugin for generating Deployment information for Raygun.io

Downloads

9

Readme

grunt-raygun-deployment

This plugin makes it easy to notify Raygun of your deployments using a grunt task.

Installation

First, install the npm package:

npm install grunt-raygun-deployment --save-dev

Then, add the following to Gruntfile.js:

grunt.initConfig({
    // Configuration to be run (and then tested).
    raygun_deployment: {
        options: {
            // You need to fill this in with your own data
            // Alternatively, set the RAYGUN_APIKEY and RAYGUN_AUTHTOKEN environment variables
            raygunApiKey: 'YOUR APPLICATIONS API KEY',
            raygunAuthToken: 'YOUR EXTERNAL AUTH TOKEN'
        }
    }
});

grunt.loadNpmTasks('grunt-contrib-uglify');

You'll need the Raygun API Key for your application, plus an External Auth Token which you can generate here.

If you don't want to check your ApiKey or AuthToken into source control, you can pass them to grunt as environment variables instead. Run RAYGUN_APIKEY="YOUR APPLICATIONS API KEY" RAYGUN_AUTHTOKEN="YOUR EXTERNAL AUTH TOKEN" grunt raygun_deployment and leave the options out of Gruntfile.js.

Finally, create a release file. We default to checking Release.yml, but you can set this path with the release option.

This is an example release file:

version: 6.0.0.0
ownerName: Jamie Penney
emailAddress: [email protected]
notes: |
    # Testing out the rake plugin

    * More markdown formatting

    ### Jamie

Once you've written this to Releases.yml, run grunt raygun_deployment and your deployment will be sent to Raygun!

If you'd rather set your release information in your Gruntfile.js you can setup 'release' as an object under the grunt settings instead.

// Project configuration.
grunt.initConfig({
  // Configuration to be run (and then tested).
  raygun_deployment: {
    options: {
      // You need to fill this in with your own data
      // Alternatively, set the RAYGUN_APIKEY and RAYGUN_AUTHTOKEN environment variables
      raygunApiKey: 'YOUR APPLICATIONS API KEY',
      raygunAuthToken: 'YOUR EXTERNAL AUTH TOKEN',
      release: {
        version: '6.1.0.0',
        ownerName: 'Jamie Penney',
        emailAddress: '[email protected]',
        notes: '#Testing out the grunt plugin\n* List item'
      }
    }
  }
});

Changelog

  • 1.1.1 - Add ability to set release info in the Gruntfile.
  • 1.1.0 - Add ability to set AuthToken and API Key as environment variables.
  • 1.0.1 - Initial release.