The application uses Version 4 of Webpack (the most recent version as of writing this) to build our application. We need to use Webpack plugins to load the various file types used in the application and Babel to utilize newer JavaScript features. The following snippet lists the devDependencies we're using in the project (taken from package.json):

...
"devDependencies": {
  "@babel/core": "^7.0.0-rc.1",
  "@babel/preset-env": "^7.0.0-rc.1",
  "babel-loader": "^8.0.0-beta.4",
  "cpp-wasm-loader": "0.7.7",
  "css-loader": "1.0.0",
  "file-loader": "1.1.11",
  "html-loader": "0.5.5",
  "html-webpack-plugin": "3.2.0",
  "mini-css-extract-plugin": "0.4.1",
  "rimraf": "2.6.2",
  "webpack": "4.16.5",
  "webpack-cli": "3.1.0",
  "webpack-dev-server": "3.1.5"
},
...

I specified exact versions for some of the libraries to ensure the application builds and runs successfully. Any libraries with a name ending in -loader or -plugin are used in conjunction with Webpack. The cpp-wasm-loader library allows us to import a C or C++ file directly, without having to compile it to Wasm first. Webpack 4 has built-in support for importing .wasm files, but you can't specify an importObj argument, which is required for modules generated with Emscripten.