Just roughly following the "Getting Started" section here: https://webpack.js.org/guides/getting-started/
Just roughly following the "Getting Started" section here: https://webpack.js.org/guides/getting-started/
- Updated my
.git/gitconfigand added my usual command aliases to work quicker with git.
git config --global alias.st status
git config --global alias.co checkout
git config --global alias.ci commit
git config --global alias.br branch
This doesn't get pushed to the repo, but my aliases are:
[alias]
st = status
co = checkout
ci = commit
br = branch
- Check if you have
npminstalled, by running the line below, you should get a version number printed to the terminal, eg: "8.1.2"
npm -v
- If you don't have
npminstalled yet, then download it here and follow the steps there to install it: https://nodejs.org/en/download/
(see "From Scratch" below)
git clone git@github.com:monello/webpack-sandbox.gitnpm install
-
Create a new repo on Github
-
Checkout the repo eg.
git clone git@github.com:monello/new-repo-name-goes-here.git -
Initialize
npm- to create thepackage.jsonfile. The-yflag means "Yes, set up thepackage.jsonwith default values and don't ask all the set-up questions"
npm init -y
At the bottom of most commits you will find notes about the code changes made during that commit. I only did this for commits with code changes that progress from the previous commit, so any commits to the README.md don't have notes or navigation. I manually added page-navigation to the commits that show progress in the form of code-changes as applied by following the course.
Some commits deal with key learning points, these I will try to list below in the "Key Commits" section.
| Comment | Description | Commit Shortcut |
|---|---|---|
| Initial Commit | Listed here to be able to get to the first commit that starts the pagnation |