- Installed webpack and webpack-cli as dev-dependencies
- Added a start script in package.json which calls webpack
- Make an index.js fil, which is the file webpack looks for by default
- Webpack spits out our code in dist/main.js by default
- Currently, the main code has nothting to do with webpack, but it will soon

- Created webpack.config.js
- Added basic configuration, including entry JS file and output dir
- Modified package.json so that webpack user our config file

- Installed style-loader and css-loader
- Configured webpack.config.js to use both loaders on css files
- The order we use these loaders in webpack.config.js matters

- Configured webpack to use ContentHash in bundle file name
- Installed HtmlWebpackPlugin to help us generate a new index.html
- It automatically includes the correct script tag at the bottom
- We passed the handlebars file as a template (including the associated json file)

- Broke our webpack.config file into 3 files
- webpack.common.js, webpack.dev.js, webpack.prod.js
- Installed webpack-merge to share the common functionality
- Updated package.json to use new config files
- Installed webpack-dev-server-and added it to start script in package.json

- Added handlebars-loaders to automatically require the files we reference in img tags
- This doesn't work as of this commit
- Added file-loader to handle svg,png,jpg files from our images
- configured file-loader to add our images to an imgs dir in build
- Also configured it to add a hash to their file names
- Added clean-webpack-plugin to our production config to clean out the build dir each time we build

- use the handlebars-loaders to load the handledbars file into an html file
- use file-loader and copy plugin to copy to build the images we need
- images are now hashed for cache busting
- handlebars template pointing to the right image sources
- still to fix the JS functionality

…clude its templates

- Extracted CSS into own file in production
- Minified CSS in production
- Added TerserJS back in to minify JS in production
- Minified HTML in production as well (however, the file is still too large because of the handlebars templates)

- updating jQuery doesn't break anything tested so far
- after testing, the seap-analytics.js needs to be loaded after the scripts.js
- until I figure how to do that with webpack, I commented it out

- created a vendor.js and added a vendor entry into webpack.common
- this should load the seap-analytics after the scripts file
- this solves an error where db would not be defined in the seap-analytics and users cannot see Your assessment section

…s compiled templates

- Helpers such as accuracy were not properly loaded
- using raw-loader we use the handlebars files as text
- then we recompile it
- hoisted db to window to eliminate reference type errors
- should remove vendor.js file and refactor script.js