Package Exports

grunt-text-replace

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (grunt-text-replace) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

grunt-text-replace

General purpose text-replacement for grunt.

This plugin allows you to replace text in files with RegEx or String replacement rules.

See the examples below for details.

Installation

Installation follows the same pattern for any grunt plugin:

Next to your project's grunt.js gruntfile, run: npm install grunt-text-replace
Then add this line to your project's grunt.js gruntfile:

grunt.loadNpmTasks('grunt-text-replace');

Usage

Here's an example of changing some text files:

grunt.initConfig({
  ...
  replace: {
    urls: {
      src: ['text/*.txt'],
      dest: 'build/text/',
      replacements: [
        { from: 'Hello', to: 'Good bye' }, 
        { from: /(f|F)(o{2,100})/g, to: 'M$2' }
      ]
    }
  }
  ...
});

Here's an example of overwriting files that have already been copied to a build directory:

grunt.initConfig({
  ...
  replace: {
    urls: {
      src: ['build/*.html'],
      overwrite: true,
      replacements: [
        { from: '"localhost"', to: '"www.mysite.com"' },
        { from: '<p>Version:</p>', to: '<p>Version: <%= grunt.template.today("yyyy-mm-dd") %></p>'}
      ]
    }
  }
  ...
});

API reference

replace

Object. The top level grunt task.

replace is is a multi-task, meaning that it must contain targets, which you can name anything you like.

replace.task.src

Array. The source of the files that require text replacement.

src must be defined within each target. src supports minimatch paths.

Examples

// One of:
src: ['test.txt']             // matches the files 'test.txt' only
src: ['test/*.html']          // matches all html files inside the folder 'test'
src: ['**/*.js']              // matches all .js files inside all subdirctories 
src: ['test.txt', '**/*.js']  // a combination of two of the above

replace.task.dest

String. The destination for those files that have are matched by the src.

dest can refer to either: a single file, or a single directory. grunt-text-replace will throw an error if multiple source files are mapped to a single file.

Examples

  dest: 'output.txt'    // sends to 'output.txt' in the grunt.js directory
  dest: 'output/'       // sends the replace files/s to the directory 'output'

replace.task.overwrite

Boolean. A switch to allow grunt-replace-text to rewrite original files.

overwrite can only be used when a dest is not defined, otherwise grunt-text-replace will throw an error.

replace.task.replacements

Array. The set of text replacements for a given task.

replacements is an array that can contain any number of replacements.

replace.task.replacements.from

String or RegEx. The old text that you'd like replace.

from matches existing text and can be a RegEx object, or a plain string.

replace.task.replacements.to

String. The new text that you'd like to change to.

to supports [grunt.template] replacements also.

Note that if you use a RegEx 'from' object, any matched items will be available to use in the 'to' string via the RegEx matching variables '$1, $2', etc.

Release History

Current version: 0.1.0