configuration

A pro-forma configuration was provided in the project setup. We will now discuss its general form.

var angularity = require('webpack-angularity-solution');

module.exports = angularity(...options|factoryFn)
  .include([modes])
  .otherwise([defaultModes])
  .resolve();

Concept

The webpack-angularity-solution is based on webpack-multi-configurator. As such it has a number of defined builds that we will call modes.

The available modes include:

• app

  Builds compositions into /app-build directory.

• release

  Builds compositions into /app-release directory. Externalised chunk manifiest and embeds into index.html.

• test

  Generates a /app/test.js test suite composed of all .spec.js files. Builds test suite into /app-test directory.

TODO

• Option globals

  Note that there are no globals in applications bundled by Webpack. If your code relies on globals such as jQuery, you will have to configure the globals option as shown above.

  Add additional globals as required by your application.

  Better practice may be to solve the problem at its source using module Shimming (see Shimming below).

• Option port

  By default --watch in the app mode will launch a BrowserSync server on port 55555. You should override this port to some unique value so that your projects to no conflict with each other.

• Options by process.env

  More than one configuration may be passed to angularity(). This means process.env may be passed in entirity (See environment variables below).

• The include() and otherwise() methods

  The include() statement runs either of the defined app|test|release compilations where the MODE environment variable.

  Omission of MODE implies the otherwise() behavior, where both app and test compilations will run. You should customise this default behavior to your taste.

  The test mode is only meaningful if you have *.spec.js files in your project.