grunt-submodule

Run Grunt across Git submodules without

grunt-submodule

Run Grunt across Git submodules.

grunt-submodule provides a Grunt task to run Grunt in a project’s submodules. You can use the submodule’s Gruntfile and node_modules or keep both outside the submodule.

$ grunt submodule:deps/*:build
        └─1─────┘ └─2──┘ └─3─┘
 
  1) this task
  2) submodule pattern
  3) grunt task to run there

This plugin requires Grunt (d’uh). You probably have used Grunt before, but just in case you’re wondering what this is all about, have a look at the Getting Started guide.

To use this plugin, you first need to install it and add it to your Gruntfile:

$ npm install grunt-submodule --save-dev
grunt.loadNpmTasks('grunt-submodule');

The submodule task tries to mimic the behavior of multi-tasks – tasks that can have multiple configurations, defined using arbitrarily named “targets.” Each submodule behaves like a target but it can be used without any explicit configuration.

If your submodules have their own Gruntfiles, you don’t need any configuration at all. Otherwise, add a section named submodule to the data object passed into grunt.initConfig() in your project’s Gruntfile.

grunt.initConfig({
  submodule: {
    options: {
      // Task-specific options go here. 
    },
    '**/*_test': {
      // Submodule-specific file lists and/or options go here. 
      options: {
      }
    }
  }
})

Type: String
Default value: Gruntfile.js

The Gruntfile to use. This is relative to the submodule path, so if you want to share the same Gruntfile with multiple submodules, just use an absolute path.

Type: String
Default value: '.'

The base directory to load Grunt tasks from if they do not exist in the submodule. If the submodule has its own node_modules or tasks directories these will take precedence over the ones inside the base directory.

Type: Array
Default value: [ 'default' ]

The tasks to run if no tasks were given on the command line.

Type: String
Default value: (empty)

Only run Grunt in the submodules that match the given pattern.

In this example, the task will just enter each submodule, run Grunt with the default task and exit.

grunt.initConfig({
  submodule: {
    options: {}
  }
});

Here we use a shared Gruntfile for all submodules and run the build and test tasks in each of them.

grunt.initConfig({
  submodule: {
    options: {
      gruntfile: __filename,
      tasks: [ 'build', 'test' ]
    }
  }
});

It is possible to override the global options for each submodule. You can either specify options fora specific submodule or use a pattern to configure multiple submodules at once.

grunt.initConfig({
  submodule: {
    options: {
      tasks: [ 'build' ]
    },
    'test/fixtures/*': {
      options: {
        tasks: [ 'build', 'test' ]
      }
    },
    'test/fixtures/test2': {
      options: {
        tasks: [ 'test' ]
      }
    }
  }
});

Sometimes you might want to filter-out some submodules that don't use Grunt. You can use the first parameter on the CLI for filtering and you can specify a default filter in your Gruntfile.

grunt.initConfig({
  submodule: {
    options: {
      filter: 'test/fixtures/test1'
    }
  }
});

Just fork the repository, send me a pull request and we’ll work out the rest together, Ok?

(Nothing yet)

License

Copyright © 2014 Jonas Pommerening

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.