The Dojo Build System¶

Author:	Rawld Gill

Introduction¶

The Dojo build system is a general-purpose program for transforming a set of resources. It was built to solve the problem of transforming a set of resources that comprise an application in order to improve the performance of that application. These kind of optimizations are termed “deployment optimizations”, and the build system includes a rich set of such optimizations.

However, the build system is not limited to these kind of transforms. At its core, the build system is an engine for applying an ordered, synchronized, configurable set of transforms to a configurable input set. Examples of other usages include document generators, style checkers, code formatters, lint checkers, and many more. In some ways it is like a make program, except the external processes that typical make programs execute can be implemented within the build system’s pluggable transform infrastructure. Of course external processes can be executed as well.

Note: the build system was completely redesigned and reimplemented in version 1.7. The pre-1.7 build system is still important to some existing installations. All historical documentation for that system is listed at The Dojo Build System Prior to version 1.7

The Build System: The top-level tutorial and reference that describes the basic operation of the build system when used for deployment optimizations.
Quick Reference for Optimization Build Program: A quick reference manual for all build system switches and knobs.

Deployment Optimization Transforms¶

The Dojo Toolkit includes the deployment optimization transforms listed below. See individual transform reference pages for complete documentation.

copy: Copies a resource from a source location to a destination location.
depsDump: Prints the module dependency graph of one or more modules.
depsScan: Determines a module’s dependencies and interns legacy dojo.cache string resources.
dojoPragmas: Applies dojo pragmas to a resource.
dojoReport: Outputs a report describing a single run of the deployment optimization transforms.
hasFindAll: Finds and optionally reports all has.js feature test usages.
hasFixup: Trims dead code branches consequent to has feature values known at build time.
hasReport: Outputs a report describing the name and location of all has.js feature tests.
insertSymbols: Inserts debugging symbols into JavaScript resources.
optimizeCss: Inlines CSS imports and/or removes comments from CSS files.
read: Reads a resource from the file system.
write: Writes a resource to the file system.
writeAmd: Writes an AMD module to the file system.
writeDojo: Outputs a module that includes the dojo loader; this transform is responsible for writing dojo.js.
writeOptimized: Processes a resource with shrinksafe or the closure compiler and writes the result to the file system.