<commit_before># bower-files

**Work in Progress!** Although tested, this module may not work as expected.
Please feel free to contribute bug reports, ideas and/or code when unexpected
behavior happens.

[![NPM version](http://img.shields.io/npm/v/bower-files.svg)](https://www.npmjs.org/package/bower-files)
[![Dependency Status](http://img.shields.io/gemnasium/ksmithut/bower-files.svg)](https://gemnasium.com/ksmithut/bower-files)
[![Code Climate](http://img.shields.io/codeclimate/github/ksmithut/bower-files.svg)](https://codeclimate.com/github/ksmithut/bower-files)
[![Build Status](http://img.shields.io/travis/ksmithut/bower-files.svg)](https://travis-ci.org/ksmithut/bower-files)
[![Coverage Status](http://img.shields.io/coveralls/ksmithut/bower-files.svg)](https://coveralls.io/r/ksmithut/bower-files)

## Installation

```bash
$ npm install bower-files --save
```

## Usage

This module is meant to help you manage your bower components and use them with task runners such as `grunt` and `gulp`.

**The Problem**

So you use bower to manage your project's front-end dependencies. That's great,
but then when you want to include those packages in your build scripts, what
then? You could have an additional config file that defines which components to
use and the paths to them, but that's just one more thing to manage. You use
bower so you don't have to have that additional step of managing your front-end
libraries.<commit_msg>updated readme with flat shields<commit_after># bower-files

[![NPM version](http://img.shields.io/npm/v/bower-files.svg?style=flat)](https://www.npmjs.org/package/bower-files)
[![Dependency Status](http://img.shields.io/gemnasium/ksmithut/bower-files.svg?style=flat)](https://gemnasium.com/ksmithut/bower-files)
[![Code Climate](http://img.shields.io/codeclimate/github/ksmithut/bower-files.svg?style=flat)](https://codeclimate.com/github/ksmithut/bower-files)
[![Build Status](http://img.shields.io/travis/ksmithut/bower-files.svg?style=flat)](https://travis-ci.org/ksmithut/bower-files)
[![Coverage Status](http://img.shields.io/coveralls/ksmithut/bower-files.svg?style=flat)](https://coveralls.io/r/ksmithut/bower-files)

Although tested, this module may not work as expected.
Please feel free to contribute bug reports, ideas and/or code when unexpected
behavior happens.

## Installation

```bash
$ npm install bower-files --save
```

## Usage

This module is meant to help you manage your bower components and use them with task runners such as `grunt` and `gulp`.

**The Problem**

So you use bower to manage your project's front-end dependencies. That's great,
but then when you want to include those packages in your build scripts, what
then? You could have an additional config file that defines which components to
use and the paths to them, but that's just one more thing to manage. You use
bower so you don't have to have that additional step of managing your front-end
libraries.
{'fraction_non_alphanumeric': 0.12840599455040871, 'fraction_numerical': 0.0, 'mean_word_length': 5.01844262295082, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 10, 'lorem ipsum': 0, 'www.': 2, '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': '6731875', 'n_tokens_mistral': 979, 'n_tokens_neox': 916, 'n_words': 278}