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-anybar

v0.2.1

Published

Grunt plugin to show the current build status in the AnyBar menu app.

Downloads

13

Readme

grunt-anybar

Grunt plugin to show the current build status in the AnyBar menu app.

Getting Started

This plugin requires Grunt ~0.4.5

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-anybar --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-anybar');

The "anybar" task

Overview

In your project's Gruntfile, add a section named anybar to the data object passed into grunt.initConfig().

grunt.initConfig({
  anybar: {
    start: {
      options: {
        // Task-specific options go here.
      }
    },
    finish: {
      options: {
        // Task-specific options go here.
      }
    }
  },
});

Last but not least, run the specific start and the finish task at the first and at the end of your grunt.registerTask() invocation:

grunt.registerTask('default', [ 'anybar:start', 'copy', 'sass:build', 'autoprefixer', 'concat', 'uglify', 'imagemin', 'jscs', 'phplint', 'anybar:finish' ]);
grunt.registerTask('dev', [ 'anybar:start', 'copy', 'connect', 'watch', 'anybar:finish' ]);

Options

options.port

Type: Integer Default value: 1738

An integer value that represents the AnyBar UDP port.

options.status

Type: String

One of AnyBar's status or color values:

  • white
  • red
  • orange
  • yellow
  • green
  • cyan
  • blue
  • purple
  • black
  • question
  • exclamation

Usage Examples

Default Options

In the example below, with default options, the plugin uses the default UDP port 1738 to talk to AnyBar.

grunt.initConfig({
  anybar: {
    start: {
      options: {
        status: 'yellow'
      }
    },
    finish: {
      options: {
        status: 'green'
      }
    }
  },
});

Custom Options

In case you use a different port you can pass the port option:

grunt.initConfig({
  anybar: {
    start: {
      options: {
        status: 'yellow',
        port: 1739
      }
    },
    finish: {
      options: {
        status: 'green',
        port: 1739
      }
    }
  },
});

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

v0.2.1

  • Fixed error hooks. So it works now.