<commit_before># grunt-envify

> Grunt plugin for envify without browserify.

This might not be what you're looking for.  If you want to set the
variables in process.env, you're looking for [grunt-env][0].  If you
want to use envify as part of browserify, you want [grunt-browserify][1].
This module is only useful if you'd like [envify][2] but without the
browserify.

[0]: https://github.com/jsoverson/grunt-env
[1]: https://github.com/jmreidy/grunt-browserify
[2]: https://github.com/hughsk/envify

## Getting Started
This plugin requires Grunt `~0.4.5`

If you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started) guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

```shell
npm install grunt-envify --save-dev
```

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

```js
grunt.loadNpmTasks('grunt-envify');
```

## The "envify" task

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

```js
grunt.initConfig({
  envify: {
    options: {
      env: {
        // Pass custom env to use instead of process.env.
      }
    },
    your_target: {
      // Target-specific file lists and/or env sandbox go here.
    }
  }
});
```

### Options

#### options.env
Type: `Object`
Default value: `process.env`

An object of env variables to use instead of process.env.

### Usage Examples

#### Default
In this example, process.env is used.

```js
grunt.initConfig({
  envify: {
    files: {
      'dest/index.js': ['src/index.js']
    }
  }
});
```

#### Custom Env
Override process.env with custom variables.

```js
grunt.initConfig({
  envify: {
    options: {
      env: {
        NODE_ENV: 'production'
      }
    },
    files: {
      'dest/index.js': ['src/index.js']
    }
  }
});
```

## 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](http://gruntjs.com/).

## Release History
_(Nothing yet)_
<commit_msg>correct task options in readme (closes #1)<commit_after># grunt-envify

> Grunt plugin for envify without browserify.

This might not be what you're looking for.  If you want to set the
variables in process.env, you're looking for [grunt-env][0].  If you
want to use envify as part of browserify, you want [grunt-browserify][1].
This module is only useful if you'd like [envify][2] but without the
browserify.

[0]: https://github.com/jsoverson/grunt-env
[1]: https://github.com/jmreidy/grunt-browserify
[2]: https://github.com/hughsk/envify

## Getting Started
This plugin requires Grunt `~0.4.5`

If you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started) guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

```shell
npm install grunt-envify --save-dev
```

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

```js
grunt.loadNpmTasks('grunt-envify');
```

## The "envify" task

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

```js
grunt.initConfig({
  envify: {
    options: {
      env: {
        // Pass custom env to use instead of process.env.
      }
    },
    your_target: {
      // Target-specific file lists and/or env sandbox go here.
    }
  }
});
```

### Options

#### options.env
Type: `Object`
Default value: `process.env`

An object of env variables to use instead of process.env.

### Usage Examples

#### Default
In this example, process.env is used.

```js
grunt.initConfig({
  envify: {
    your_target: {
      files: {
        'dest/index.js': ['src/index.js']
      }
    }
  }
});
```

#### Custom Env
Override process.env with custom variables.

```js
grunt.initConfig({
  envify: {
    your_target: {
      options: {
        env: {
          NODE_ENV: 'production'
        }
      },
      files: {
        'dest/index.js': ['src/index.js']
      }
    }
  }
});
```

## 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](http://gruntjs.com/).

## Release History
_(Nothing yet)_

{'fraction_non_alphanumeric': 0.12808609411268201, 'fraction_numerical': 0.004009284659210804, 'mean_word_length': 3.313011828935396, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5156617', 'n_tokens_mistral': 1552, 'n_tokens_neox': 1506, 'n_words': 536}