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-run-if-branch-modified

v0.1.0

Published

Run grunt tasks according to changed files of the branch.

Downloads

1

Readme

grunt-run-if-branch-modified

Build Status

Run grunt tasks according to changed files of the branch.

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-run-if-branch-modified --save-dev

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

grunt.loadNpmTasks('grunt-run-if-branch-modified');

The "run_if_branch_modified" task

Overview

This plugin switches tasks to run or not according to changed files of current branch.

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

grunt.initConfig({
  run_if_branch_modified: {
    your_target: {
      file_patterns: ['*.js', '*.json'],
      tasks: ['test']
    },
  },
});

The plugin executes git diff --name-only HEAD master and checks these files matches any file patterns. And executes tasks if any file has matched.

This plugin suppose to be used with the scenario such as Pull Request testing by CI. For instance, run the test which is taking long time, only when related codes are edited.

Arguments

file_patterns

Type: Array

List of file globbing patterns. If any changed files of the branch is matched to these patterns, the plugin executes registered tasks. The format of patterns are same to grunt.file.match.

tasks

Type: Array

List of tasks to execute if the condition is matched.

Usage Examples

In this example, the test task full_test takes very long time. Run the test only when the core source (src/core/*.js) is modified.

grunt.initConfig({
  run_if_branch_modified: {
    full_test: {
      file_patterns: ['src/core/*.js'],
      tasks: ['full_test']
    },
  },
});

grunt.registerTask('full_test', ['some-very-long-test', 'another-long-test']);
# execute this in CI.
grunt run_if_branch_modified:full_test

Release History

  • v0.1.0 Initial release.