<commit_before>![React Boilerplate](img/react-boilerplate.png)

A production-ready es2015 boilerplate for React projects using Node 4.2.

## Getting Started

1. Install your packages with `npm install`

2. Run The local server with `npm start` in one terminal window.

3. Run the sass watch script with `npm run sass-watch` in another terminal window.

4. Visit your site at http://localhost:4001. If you see "Hello World", you know you're swagging.

## Deploying for production

  Deploying to production is simple:
  
  1. Run `npm run build`.
  2. Commit and push your changes to your remote.
  3. (No need if using Heroku) Pull your changes on your live server

## Environment Variables
- In development you can override any environment variables in a .env file. See [this](https://github.com/motdotla/dotenv) for details. Make sure you keep .env in your gitignore.
- In production, you can just set your environment variables as usual.
- If you set an `API_URL` environment variable, it will be available to your app at `window.API_URL` since we have passed it to index.ejs. This is useful for having different endpoints in production and development.

# Credits<commit_msg>Revert "Revert "No more reason for our version""<commit_after>![React Boilerplate](img/react-boilerplate.png)

A production-ready es2015 boilerplate for React projects using Node 4.2.

Not sure this needs to exist anymore. In favor of [this](https://github.com/facebookincubator/create-react-app)

## Getting Started

1. Install your packages with `npm install`

2. Run The local server with `npm start` in one terminal window.

3. Run the sass watch script with `npm run sass-watch` in another terminal window.

4. Visit your site at http://localhost:4001. If you see "Hello World", you know you're swagging.

## Deploying for production

  Deploying to production is simple:
  
  1. Run `npm run build`.
  2. Commit and push your changes to your remote.
  3. (No need if using Heroku) Pull your changes on your live server

## Environment Variables
- In development you can override any environment variables in a .env file. See [this](https://github.com/motdotla/dotenv) for details. Make sure you keep .env in your gitignore.
- In production, you can just set your environment variables as usual.
- If you set an `API_URL` environment variable, it will be available to your app at `window.API_URL` since we have passed it to index.ejs. This is useful for having different endpoints in production and development.

# Credits
{'fraction_non_alphanumeric': 0.07302474062250598, 'fraction_numerical': 0.013567438148443736, 'mean_word_length': 4.014, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 3, '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': '1707622', 'n_tokens_mistral': 724, 'n_tokens_neox': 685, 'n_words': 355}