<commit_before>What is the Emberella Component Blueprint?
==========================================

The goal of the Emberella Component Blueprint project is to streamline the
process of creating individual [Ember][ember] components, modules, or "micro-projects."

It is intended as a starting point (or project template) for developers to build
their own fully-tested, modular [Ember Components][ember-components].

**Please report any issues you encounter while using the instructions
provided here.**

Get Started
==========================================

Step 1: Clone this repository.

```
$ git clone <EMAIL>:realityendshere/emberella-component-blueprint.git
```

Step 2: Switch to the project directory

```
$ cd emberella-component-blueprint
```

Step 3: Install all dependencies with NPM

```
$ npm install
```

Project Setup
==========================================

Step 1: Start your own repo by removing the `.git` directory and
reinitializing Git.

```
$ rm -R .git; git init
```

Step 2: Configure NPM

```
$ npm init
```

Follow the prompts to setup your project for NPM. Default values are in (parentheses).

```
name: (emberella-component-blueprint)
version: (0.0.0)
git repository:
keywords:
author:
license: (ISC)
Is this ok? (yes)
```

Step 3: Configure Bower

```
$ bower init
```

Follow the prompts to setup your project for Bower. Default values are in (parentheses).

Notes:
+ You can probably leave "main file" blank.
+ For module types, select `amd` and `globals`.

```
[?] name: (emberella-component-blueprint)
[?] version: (0.0.0)
[?] description:
[?] main file:
[?] what types of modules does this package expose?
[?] keywords:
[?] authors:
[?] license: (MIT)
[?] homepage:
[?] set currently installed components as dependencies? (y/N)
[?] add commonly ignored files to ignore list? (Y/n)
[?] would you like to mark this package as private which prevents it from being accidentally published to the registry? (y/N)
[?] Looks good? (Y/n)
```

Step 4: Configure module output

Open the `output.js` file and provide your project with a global namespace and
a package name.

```
module.exports = {
  global: 'YOUR_GLOBAL_NAMESPACE',
  packageName: 'YOUR_PACKAGE_NAME',
  main: 'main',
  shim: {
    'ember': 'Ember'
  }
};
```

Get to Work
==========================================

To begin development and testing of your component:

```
$ ./testem
```

With the testing server running, [view the example component][example] to see
your component in a browser.

Your tests and component page will reload automatically when you save changes
to your code.<commit_msg>Updated README regarding global namespace config<commit_after>What is the Emberella Component Blueprint?
==========================================

The goal of the Emberella Component Blueprint project is to streamline the
process of creating individual [Ember][ember] components, modules, or "micro-projects."

It is intended as a starting point (or project template) for developers to build
their own fully-tested, modular [Ember Components][ember-components].

**Please report any issues you encounter while using the instructions
provided here.**

Get Started
==========================================

#### Step 1: Clone this repository.

```
$ git clone <EMAIL>:realityendshere/emberella-component-blueprint.git
```

#### Step 2: Switch to the project directory

```
$ cd emberella-component-blueprint
```

#### Step 3: Install all dependencies with NPM

```
$ npm install
```

Project Setup
==========================================

#### Step 1: Start your own repo by removing the `.git` directory and
reinitializing Git.

```
$ rm -R .git; git init
```

#### Step 2: Configure NPM

```
$ npm init
```

Follow the prompts to setup your project for NPM. Default values are in (parentheses).

```
name: (emberella-component-blueprint)
version: (0.0.0)
git repository:
keywords:
author:
license: (ISC)
Is this ok? (yes)
```

#### Step 3: Configure Bower

```
$ bower init
```

Follow the prompts to setup your project for Bower. Default values are in (parentheses).

Notes:
+ You can probably leave "main file" blank.
+ For module types, select `amd` and `globals`.

```
[?] name: (emberella-component-blueprint)
[?] version: (0.0.0)
[?] description:
[?] main file:
[?] what types of modules does this package expose?
[?] keywords:
[?] authors:
[?] license: (MIT)
[?] homepage:
[?] set currently installed components as dependencies? (y/N)
[?] add commonly ignored files to ignore list? (Y/n)
[?] would you like to mark this package as private which prevents it from being accidentally published to the registry? (y/N)
[?] Looks good? (Y/n)
```

#### Step 4: Configure module output

Open the `output.js` file and provide your project with a global namespace and
a package name.

```
// Replace with your own global namespace.
var MY_JS_GLOBAL_NAMESPACE = 'GlobalNamespace';

// Replace with your own package name.
var MY_JS_PACKAGE_NAME = 'replace-me';
```

**Note: you will need to restart test'em (if it is running) for tests to pickup
any changes to the global namespace**

Get to Work
==========================================

To begin development and testing of your component:

```
$ ./testem
```

With the testing server running, [view the example component][example] to see
your component in a browser.

Your tests and component page will reload automatically when you save changes
to your code.
{'fraction_non_alphanumeric': 0.1673130193905817, 'fraction_numerical': 0.004801477377654663, 'mean_word_length': 4.855135135135135, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, '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': '3966003', 'n_tokens_mistral': 1627, 'n_tokens_neox': 1527, 'n_words': 651}