<commit_before># BoReLESS - Grunt Bower + RequireJS + LESS Boilerplate

This is a boilerplate to ease builds of web projects utilising RequireJS, having several JS library dependencies. Unlike Yeoman & other tools, this is a pure Grunt script with full transparency on how the build is handled; there is no magic.

## Installation

If you don't already have node.js 0.8.x or later, fetch it from [nodejs.org](http://www.nodejs.org/). In addition we need a few dependencies you may have.

    > npm install -g bower grunt

Installing the project itself is easy. Both build system dependencies and app dependencies are triggered by

    > npm install

It actually performs a release build, too (to verify that everything is ok).

## Building

To trigger **debug** build

    > grunt debug

To trigger **release** build

    > grunt release

## Running the Service

Most likely the normal *grunt server* will fail (yet there is no big reason why it should). The system comes with bundled *node/express* stack, because that is likely you would use for development use, anyway. Start the server in **debug** mode by

    > npm start
   
Note that if you have run *grunt debug* in another window, it should be rebuilding your changed pages in the background.
<commit_msg>Depend on grunt-cli since it is used to trigger build<commit_after># BoReLESS - Grunt Bower + RequireJS + LESS Boilerplate

This is a boilerplate to ease builds of web projects utilising RequireJS, having several JS library dependencies. Unlike Yeoman & other tools, this is a pure Grunt script with full transparency on how the build is handled; there is no magic.

## Installation

If you don't already have node.js 0.8.x or later, fetch it from [nodejs.org](http://www.nodejs.org/). In addition we need a few dependencies you may have.

    > npm install -g bower grunt-cli

Installing the project itself is easy. Both build system dependencies and app dependencies are triggered by

    > npm install

It actually performs a release build, too (to verify that everything is ok).

## Building

To trigger **debug** build

    > grunt debug

To trigger **release** build

    > grunt release

## Running the Service

Most likely the normal *grunt server* will fail (yet there is no big reason why it should). The system comes with bundled *node/express* stack, because that is likely you would use for development use, anyway. Start the server in **debug** mode by

    > npm start
   
Note that if you have run *grunt debug* in another window, it should be rebuilding your changed pages in the background.

{'fraction_non_alphanumeric': 0.059052059052059055, 'fraction_numerical': 0.001554001554001554, 'mean_word_length': 3.8402255639097747, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 13, 'https://': 0, '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': '3152458', 'n_tokens_mistral': 691, 'n_tokens_neox': 652, 'n_words': 385}