Tools to build a project from almost any source to an output structure
Want to see pretty graphs? Log in now!
npm install buildproject
|14||downloads in the last week|
|28||downloads in the last month|
|Last Published By|
|Version||0.0.8 last updated a year ago|
|Dependencies (9)||commands, hogan.js, htmlparser, less, readdir, task-runner, uglify-js, unit-test, xhrequest|
Series of tools to build source content into a web app.
Install using npm:
npm install buildproject or check out the latest version from Git.
Once installed, run using the binary:
buildproject optional commands can be used to add features. The most useful are:
-profile profilename used to run a specific profile, by default will run the profile called "full" or when that isn't found, runs the first profile found.
-config fullpath used to set the path to the configuration JSON file, either to the JSON file itself or to the container directory so long as the file is called
Additional configuration can be either set in the command line or in the JSON file as part of a profile / settings:
-sourcePath fullpath sets the path of the source files, will be prepended to all source content paths in the configuration JSON. If omitted the default is the 'src' directory at the same level as the
-targetPath fullpath sets the path of the output files, will be prepended to all output content paths in the configuration JSON. If omitted the default is the 'web' directory at the same level as the
--verbose prints a lot of information to the console as the build is running
Detailed configuration for the build can be supplied in a JSON file (usually called
buildproject.json) that should have the following properties:
A map of string arrays, the names in the map are the names of the profiles. Use these to split out types of task, for example the debug versus production profile.
The full path to the source directory - this is prepended to the path in all source tasks. When omitted (or empty) this will default to a directory named 'src' at the same level as the JSON file.
The full path to the output directory - this is prepended to the path in all output tasks. When omitted (or empty) this will default to a directory named 'web' at the same level as the JSON file.