syncing fork repo

.eslintrc.json

@@ -53,6 +53,7 @@
     "no-var": 2,
     "prefer-arrow-callback": 1,
     "prefer-const": 2,
+    "prefer-template": "error",
     "quotes": [1, "single"],
     "semi": [1, "never"],
     "space-before-blocks": ["error", { "functions": "always", "keywords": "always", "classes": "always" }],

.gitignore

@@ -8,6 +8,7 @@ coverage/
 docs/
 sessions/
 screenshots/*
+out/
 
 # sqlite databases
 # *.db

01 Setup Win10.md

@@ -0,0 +1,60 @@
+
+# Setup for Windows 10 Users
+
+The tools used in this module are designed to be used in a Unix or Linux environment. Whilst this will create challenges for Windows 10 user there are some steps you will need to take. Please read and follow the steps below carefully:
+
+Install the Windows Subsystem for Linux (WSL). Open PowerShell as Administrator and run:
+
+``` shell
+Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
+```
+
+Restart your computer when prompted.
+
+Now install Visual Studio Code and once launched install the [remote-wsl](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl) component by Microsoft. You should also install the [browser-preview](https://marketplace.visualstudio.com/items?itemName=auchenberg.vscode-browser-preview) component which will allow you to open html web pages.
+
+![remote-wsl](exercises/.images/remote-wsl.png)
+
+Now you need to install Ubuntu. This can be found by searching for `run linux on windows` in the Microsoft Store. You will be presented with the following screen.
+
+![Microsoft Store](exercises/.images/store.png)
+
+Choose the Ubuntu operating system (v18.04 LTS) and install. Once installed, click on the **Launch** button, this will open a console window and you will need to wait for a few minutes for the installation to complete.
+
+## Cloning the Forked Repository
+
+You will now need to fork the foundation lab by clicking on the Fork button. This will create a copy of the repository. See the standard setup instructions for more details.
+
+Now you can clone your forked repository by running the following command in the Ubuntu console, replacing xxx with the URL of your repository.
+
+```shell
+git clone xxx
+```
+
+This will create a directory called `foundation` in the Ubuntu console. The final step is to launch VS Code from within the WSL environment by running the following command:
+
+```shell
+code foundation
+```
+
+This will launch VS Code from within the WSL with the contents of the `foundation/` directory. If you open the integrated terminal (using the **Terminal** menu) you will see that you have the full ubuntu bash shell. You can now run all the remaining steps from this integrated terminal, just as you would for a standard Linux install.
+
+## Installing NodeJS
+
+These steps are identical to those used on a full Ubuntu installation. Start by installing the Node Version Manager (NVM) tool:
+
+```shell
+curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.0/install.sh | bash
+nvm --version
+nvm install node
+```
+
+If the `nvm` command is not found you will need to reload the shell:
+
+```shell
+source ~/.profile
+```
+
+Now try to install again.
+
+Now you can go directly to step 4 in the standard setup instructions.

01 Setup.md

@@ -3,7 +3,9 @@
 
 In this worksheet you will learn how to configure your work environment using VS Code. You should start by installing **Visual Studio Code** (NOT VISUAL STUDIO!) from the [website](https://code.visualstudio.com), note that it might already be installed. If you are using a Coventry University computer and the software is not installed you can do this using AppsAnywhere.
 
-If you are using Windows 10 you will also need to install [Git](https://git-scm.com/download/win), this may already be installed on a Coventry University computer.
+If you are using Windows 10 you will also need to install [Git](https://git-scm.com/download/win), this may already be installed on a Coventry University computer. If you are on MacOS you may already have it installed as it comes with the XCode IDE but if you have recently updated your OS you may need to run the `xcode-select --install` command to update the **Xcode Command-line Tools** but if you don't want to install XCode you can install git using [HomeBrew](http://brew.sh/) using the `brew install git` command. If you are running Ubuntu you can install it using the `sudo apt install git` command.
+
+DO NOT INSTALL THE GIT GUI TOOLS!
 
 Visual Studio Code comes with an integrated **Terminal** that can be used instead of the standard _Command Prompt_ or _Terminal_. If you are using Linux or MacOS this will give you a Bash prompt however on Windows 10 it defaults to the _Command Prompt_ and will need to be changed to the _Bash Shell_.
 
@@ -139,14 +141,43 @@ $ node index.js
 
 Now we have the server up and running so the final task is to view the web page using the web browser. Simply open the Chrome browser and navigate to localhost:8080 where you should see a message. If this works you are ready to start the lab exercises.
 
-## 5 Pushing the Changes to GitHub
+## 5 Using npm and its package.json
+
+**Have a look at your `package.json` file and understand its contents**.
+- When you are starting a new _project_, **you have to create this yourself**:
+
+1. Use the `npm init` command to create the package.json file
+	- You can leave all the options default, just leave them empty and keep pressing enter
+	- Alternatively you can run `npm init --yes`, it will simply leave everything default
+2. Install the dependencies for the first time using the `-S` _switch_ with `npm install`
+	- e.g.: `npm install -S koa koa-bodyparser`
+		- This would add something like this to the `package.json` file:
+			```json
+			"dependencies": {
+			"koa": "^2.11.0",
+			"koa-bodyparser": "^4.2.1"
+			}
+			```
+	- When you next run `npm install -S <package>`, the given package's _newest version_ will be simply added to the list, or in case of a new version for a _previously listed_ dependency, the _version number_ will be updated
+	- This `-S` is just a short version of the `--save` _switch_
+		- **You can use the alternative `--save-dev` switch to install and save them as _development dependencies_**
+			- Something that you wouldn't want to deploy, but is necessary for development
+				- E.g. we will use `jest` for testing, and `eslint` for linting during the development phase, but these shouldn't be required to be installed during deployment
+	- You are done with adding the dependencies, now simply use `npm install` to install all of them at once!
+		- If you don't want to install development dependencies, use `npm install --production`
+3. This `package.json` file is also useful to store _scripts_:
+	- Look at the following line: ` "start": "nodemon index.js"`
+	- This lets us simply type `npm start` in the terminal to start our application via _nodemon_
+		- Nodemon is a great tool that restarts the application every time we save a file in the given folder, so we don't actually have to manually stop and restart it after every modification.
+
+## 6 Pushing the Changes to GitHub
 
 As you work through the lab activities two things are likely to happen:
 
 1. You make changes to the code that you want to push to the forked copy of your repository.
 2. You will need to pull any bug fixes from the original repository.
 
-### 5.1 Configuring the Repository
+### 6.1 Configuring the Repository
 
 Before you start interacting with the GitHub server you need to configure the local repository. Open the Bash Shell and run the following commands:
 
@@ -157,7 +188,7 @@ git config user.email 'doej@coventry.ac.uk'
 
 remember to replace the values with you own name and your university email (but without the uni part).
 
-### 5.2 Pushing Changes
+### 6.2 Pushing Changes
 
 **NOTE: You only need to carry out this step when you have make changes to the code! This will normally need to take place each time you complete a "Test Your Understanding" section.**
 
@@ -175,7 +206,7 @@ Now you should click on the **Sync** icon (shown below) to push the new commit u
 
 At this point you should be able to refresh your GitHub repository page to see the changes.
 
-### 5.3 Pulling from Upstream
+### 6.3 Pulling from Upstream
 
 As new materials and resources are added to the original repository (and bugs fixed) you will want to merge these into your forked repository. Before you can do this you will need to add a link to the upstream repository. Open a bash shell: