Checklist for the Windows Subsystem for Linux

Required:

• Enable WSL Feature through Windows.
• Download Ubuntu from the Windows Store.
• Setup Ubuntu Username and password.

Recommend:

• Update your terminal profile.
• Setup aliases to help with navigation.
• Review recommended work-flow and software installation notes.

Optional:

• Create a top-level NPM package.json to hold Windows-Side global packages.
• Install VSCode
• Install Git on the Windows Side for use with VSCode SCM.

Challenge:

• Install and run live-server with a sample HTML file.

Once you have completed the above steps, try to figure out how to get 'live-server' from NPM running on your machince.

There are instructions in the guide, but before you read those, try to figure out how you would get this up and running with this new WSL work-flow. This will give you the chance to safely play with things on both systems, teach you how to troubleshoot between the two, and ultimatly will help strengthen your work-flow.

Some context on what live-server is:

Live-server allows you to setup a simple development server which will load a sample HTML page in your browser. It also has a hot-reload feature that detects when you make a change to a file, and automatically reloads the web page for you.

It uses NPM, but also makes use of your browser, so you must take those things into consideration when installing it and trying to use it. NPM also uses a heirarchy structure when looking for packages. This means that it will look at your current working directory for the package first, and then look upwards until it reaches the top-most level.

Note that NPM may exist on both the Linux side as well as the Windows side. How does the WSL work-flow account for this? Which NPM should you use? Are you able to use the --global flag? Why or why not?

Expected result:

You will know you are done when you are able to type live-server into your working directory's commandline and have it open the sample HTML page, and hot-reload it when you make a change to the file.