<commit_before># Seneca 2017 Learning Lab

## Introduction

In this lab series we will explore a number of open source and GitHub tooling,
automation, and worflow options.  You will learn about how to build node.js modules,
how to use tools like linters, code formatters, how to use unit tests, how to do automated
checks on your commits and pull requests, etc.

We will expand on this repo in the coming weeks, so it's important for you to finish
each week's tasks before the next lab.  If you get stuck, feel free to help one another.
This is not a test, but a learning exercise.

## Create a Repo

This repo will form the basis of our exploration of various open source tooling.
Begin by creating a repo of your own similar to this one. Use https://github.com/new
to create your new repo.  Make sure you include the following:

* Initialize with a `README.me` file
* Add a `.gitignore` for `Node` (e.g., node.js)
* Add a `License` using the [MIT License](https://opensource.org/licenses/MIT)

It will look something like this:

![Create New GitHub Repo](screenshots/create-repo.png)

## Clone your repo

After you've created it on GitHub, you need to clone it locally:

```bash
$ git clone git@github.com:<github-username>/<repo-name>.git
```

## Initialize a new Node.js Module

You should already have [node.js](https://nodejs.org/) installed.  If you don't,
do it now.

Next use [npm](https://docs.npmjs.com/) (NOTE: `npm` gets installed along with node.js)
to initialize your `package.json` file.

**FYI:** Be aware that according to [this information](https://github.com/npm/npm/issues/14257), if you use Git Bash, you will not be able to confirm the "Is this ok? (yes)" question at the end. 
In this case(if you use Windows), just for this step, I would advice you to use cmd.exe, as it seems that CMD doesn't have the issue mentioned above.

```bash
$ npm init

This utility will walk you through creating a package.json file.<commit_msg>Added the information that people can face problems with GitBash when they run npm init<commit_after># Seneca 2017 Learning Lab

## Introduction

In this lab series we will explore a number of open source and GitHub tooling,
automation, and worflow options.  You will learn about how to build node.js modules,
how to use tools like linters, code formatters, how to use unit tests, how to do automated
checks on your commits and pull requests, etc.

We will expand on this repo in the coming weeks, so it's important for you to finish
each week's tasks before the next lab.  If you get stuck, feel free to help one another.
This is not a test, but a learning exercise.

## Create a Repo

This repo will form the basis of our exploration of various open source tooling.
Begin by creating a repo of your own similar to this one. Use https://github.com/new
to create your new repo.  Make sure you include the following:

* Initialize with a `README.me` file
* Add a `.gitignore` for `Node` (e.g., node.js)
* Add a `License` using the [MIT License](https://opensource.org/licenses/MIT)

It will look something like this:

![Create New GitHub Repo](screenshots/create-repo.png)

## Clone your repo

After you've created it on GitHub, you need to clone it locally:

```bash
$ git clone git@github.com:<github-username>/<repo-name>.git
```

## Initialize a new Node.js Module

You should already have [node.js](https://nodejs.org/) installed.  If you don't,
do it now.

Next use [npm](https://docs.npmjs.com/) (NOTE: `npm` gets installed along with node.js)
to initialize your `package.json` file.

**FYI:** Be aware that according to [this information](https://github.com/npm/npm/issues/14257), if you use Git Bash, you will not be able to confirm the "Is this ok? (yes)" question at the end. 
In this case(if you use Windows), just for this step, I would advice you to use cmd.exe to run `npm init` command, as it seems that CMD doesn't have the issue mentioned above.

```bash
$ npm init

This utility will walk you through creating a package.json file.
{'fraction_non_alphanumeric': 0.08658658658658659, 'fraction_numerical': 0.0045045045045045045, 'mean_word_length': 4.072335025380711, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 10, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 2, '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': '5227040', 'n_tokens_mistral': 1193, 'n_tokens_neox': 1120, 'n_words': 606}