Vital Software front-end asset builder
Webpack development and bundling tool for Vital Software.
All changes that are pushed to the master branch are deployed via a Buildkite pipeline. The pipeline runs tests, builds a Docker image, builds the release artifacts for NPM, and the library itself to an NPM registry. Use the Commit Message as documented in our Contributing Guide to trigger a release.
To install, run the following commands:
yarn add vitalizer -D
To run Vitalizer in development mode (using webpack-serve), run the following command:
To build your project files for production, run the following command:
To configure Vitalizer, create a file called
.vitalizer in the root of your project:
And set any of the following variables:
|:x:||:white_check_mark:||When set, production assets are output as |
|:large_orange_diamond:||:white_check_mark:||When set to |
|:x:||:white_check_mark:||When set to |
|:white_check_mark:||:x:||By default, the development web server binds to |
|:white_check_mark:||:white_check_mark:||Comma seperated list of HTML files to use. Defaults to |
|:white_check_mark:||:x:||By default, the development web server will attempt to listen on port 3000 or prompt you to attempt the next available port. You may use this variable to specify a different port.|
|:white_check_mark:||:white_check_mark:||Comma seperated list of module roots to use other than |
Expand variables already on your machine for use in your
.env file (using dotenv-expand).
For example, to use the
DOMAIN=www.example.com FOO=$DOMAIN/foo BAR=$DOMAIN/bar