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-change-scanner

v0.0.4

Published

Grunt task that scans src files for changes based on RegExp pattern. Found changes are reported into a file with Markdown format.

Downloads

6

Readme

grunt-change-scanner

Grunt task that scans src files for changes based on RegExp pattern. Found changes are reported into a file with Markdown format.

Getting Started

This plugin requires Grunt ~0.4.2

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-change-scanner --save-dev

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

grunt.loadNpmTasks('grunt-change-scanner');

The "change_scanner" task

Overview

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

grunt.initConfig({
  change_scanner: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
});

Options

options.pattern

Type: String

No default value: this is a required option

A RegExp pattern that will match for whatever you want to look for. It's expected to have single capturing group:

(?:<.*?data-something=")(.*?)(?:".*?>)

Would match opening tag of HTML element with data-something attribute:

<a href="#" data-something="foo">

The capturing group would return foo in this case.

options.banner

Type: String

A banner value that will be appended after ## separator:

'<%= grunt.template.today("yyyy-mm-dd HH:MM") %>'

Would result with something similar to this:

### 2014-02-13 09:59

Usage Examples

In this example scanner will look for changes to values of data-something attributes of HTML elements in specified src/index.html document. The changes will be reported to report/changes.md file.

grunt.initConfig({
  change_scanner: {
    options: {
        pattern: '(?:<.*?data-something=")(.*?)(?:".*?>)',
        banner: '<%= grunt.template.today("yyyy-mm-dd HH:MM") %>'
    },
    files: {
      'report/changes.md': ['src/index.html'],
    }
  }
});

Example of generated report in Markdown format

# Current
bar
qux
## v3
### Added
qux
### Removed
buz

## v2
### Added
buz

## v1
### Added
bar

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

  • 0.0.3 - Added double space before line breaks
  • 0.0.2 - First public release