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

v0.2.0

Published

The last build tool you'll ever need

Downloads

34

Readme

grunt-gobble

Gobble is the last build tool you'll ever need.

Getting Started

First things first: you don't need Grunt to run Gobble. All you need is gobble-cli and a build definition known as a gobblefile.

But if you're already using Grunt and want to integrate Gobble, or you want to manage multiple build definitions, you can do so by installing the plugin:

npm install grunt-gobble --save-dev

Once the plugin has been installed, add this to your Gruntfile:

grunt.loadNpmTasks( 'grunt-gobble' );

Psst! If you're looking for a more streamlined way to organise Grunt tasks and config, check out http://bit.ly/grunt-happy.

The "gobble" task

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

grunt.initConfig({
  gobble: {
    your_target: {
      // required for building the project
      dest: 'tmp/build',

      // optional - which port to use if serving the project. Defaults to 4567
      port: 5678,

      // optional - typically 'development' or 'production'. Defaults to 'development'.
      // The environment can be determined inside a build definition with `gobble.env()`
      environment: 'production',

      // optional - whether to always empty the contents of `dest`. If `false`, this
      // task will fail if `dest` is not empty. Defaults to `false`
      force: true,

      // optional - a string (path to build definition, relative to project root) or a
      // function that returns a gobble node. Defaults to 'gobblefile.js'
      config: function () {
        var gobble = require( 'gobble' );
        return gobble( 'src' ).transform( 'uglify-js' );
      }
    },
  },
});

Serving your project

You can serve your project with the following command:

grunt gobble:your_target:serve

To build the project, omit the :serve or replace it with :build:

grunt gobble:your_target

If you run grunt gobble without specifying a target, all targets (if there are more than one) will be built.

Contributing

Usual drill - try to adhere to existing conventions, add tests for any new features. Thanks!

License

MIT.