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-regex-replacer

v0.1.1

Published

Find and replace for grunt

Downloads

366

Readme

grunt-regex-replacer

Searches through files using regular expressions, and replaces the matches found.

Getting Started

This plugin requires Grunt ~0.4.5

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-regex-replacer --save-dev

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

grunt.loadNpmTasks('grunt-regex-replacer');

The "regex_replacer" task

Overview

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

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

Data

data.src

Type: glob Required

The files to search through.

data.regex

Type: regex Required

This is the regex that will be used to find places in the data.src files that should be changed. This can be a single regular expression, or an array of regular expressions.

data.replacement

Type: string or function Required

If this is a string, each match found using data.regex will be replaced with data.replacement.

If this is a function, each match found using data.regex will be passed to the function. The function should return the string that will replace the match.

For example, to simply replace all matches with the work 'REPLACE', you could do the following:

replacement: 'REPLACE'

Or, to append a string to each match, you could do the following:

replacement: function (match) {
  return match + ' additional text';
};

Usage Examples

String replacement

In this example, all occurrences of the string ORIGINAL are replaced with REPLACEMENT in the file tmp/string.html.

grunt.initConfig({
  regex_replacer: {
    string: {
      src: 'tmp/string.html',
      regex: /ORIGINAL/g,
      replacement: 'REPLACEMENT'
    }
  }
});

Function replacement

In this example, all occurrences of the string ORIGINAL are appended with ' addtional text' in the file tmp/function.html.

grunt.initConfig({
  regex_replacer: {
    function: {
      src: 'tmp/function.html',
      regex: /ORIGINAL/g,
      replacement: function (match) {
        return match + ' additional text';
      }
    }
  }
});

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

(Nothing yet)