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-bower-event

v0.4.0

Published

Now Grunt is talking your Bower language, listening for answers.

Downloads

8

Readme

grunt-bower-event

Built with Grunt Build Status Coverage Status Dependencies Dev Dependencies

Now Grunt is talking your Bower language, listening for answers.

Getting Started

This plugin requires Grunt ~0.4.0

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-bower-event --save-dev

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

grunt.loadNpmTasks('grunt-bower-event');

This plugin was designed to work with Grunt 0.4.x. If you're still using grunt v0.3.x it's strongly recommended that you upgrade, but in case you can't please use v0.3.2.

Bower task

Run this task with the grunt bower command.

Task targets, files and options may be specified according to the grunt Configuring tasks guide.

Options

bowerDirectory

Type: String

Default: current working directory of grunt

Bower working directory where your .bowerrc configuration is located.

config

Type: Object

Default: empty, Bower default config

Bower configuration according to the specification. Leave blank for Bower's default config.

arguments

Type: Array

Default: empty

Arguments that are passed to the bower command. Leave blank if command does not take arguments.

Example: ['bootstrap'] for command 'bower install'.

argumentOptions

Type: Object

Default: empty

Argument options that are passed to the bower command.

Example: {"force-latest": true} for command bower install

eventPrefix

Type: String

Default: bower.

Bower events are namespace-prefixed with this label when they are emitted through the grunt.event API.

Example: listen for a log event with grunt.event.on('bower.log', function (data) { ... })

Usage Examples

Simple Bower command

bower: {
  install: {
  }
}

The above configuration will run bower install.

Just give the desired bower command as grunt target. The list of commands is available at Bower's API documentation

Explicit Bower command

bower: {
  customTarget: {
    command: 'list'
  }
}

The above configuration will run bower list.

Subscribe to Bower events

grunt.event.on('bower.end', function (data, command) {
  console.log("received data from command: " + command);
  console.log(data);
});

Events from bower commands are emitted through the grunt.event API. The events are log, error, end, and prompt. They are prefixed with the option given by eventPrefix, e.g. "bower.end" in the example above.

The callback takes two parameters: the data object that the bower command produced and a string argument command, e.g. "install".

TODO

more samples to come..

Release History

  • 2016-03-13 v0.4.0 Release for #5. Version bumps.
  • 2015-02-14   v0.3.1   Release for #3 and #4.
  • 2014-12-29   v0.3.0   NPM registry version fixes. I encourage you to use v0.3.0 and later.
  • 2014-12-29   v0.2.1   Filter events by bower command (see issue #2).
  • 2014-08-25   v0.2.0   Publish a version to npm registry.
  • 2013-07-11   v0.1.0   First version.