Fix to obey --build-dir when copying files
Based off the original build.json and committed output files, it appears 3-copy.js build files were intended for assets, not assets-global. Specifying `global-config: false` will make this happen.
Update to test #9's build.json to reflect the change in target paths for copy commands from commit 484f02
Merge pull request #79 from derek/buildcopy-fix

Fix to obey --build-dir when copying files
Version 0.4.0.
adding support for assets on css modules, which should also honor the cssproc config
I know how much @ericf loves the breakline at the end, jejeje
I know how much @ericf loves the breakline at the end, jejeje
bumping version for 0.4.1 release
updated docs
adding newline
Merge pull request #86 from caridy/cssassets

version 0.4.1: adding support for assets on css modules
Lock istanbul to v0.1.37 to prevent breaking coverage comparison tests.
Omit assets in non-skinnable builds when mod.assets === false

When a module's build config includes the "assets" property set to `false`,
we should skip copying any existing assets folder for that build target.

However, if that module's meta.json includes the "skinnable" property set
to true, the assets directory will still be copied, as it is required by
the skinning pattern.

Fixes #87
Merge pull request #91 from zillow/lock-istanbul

Lock istanbul to v0.1.37 to prevent breaking coverage comparison tests
Merge pull request #92 from zillow/omit-assets

Omit assets in non-skinnable builds when mod.assets === false
bumping version. adding new npm command to generate docs easily. updated docs.
move `args.unshift(util.shifter)` out of walk.js's run() loop

The path 'shifter/bin/shifter' was prepended to the spawn argument list
on each iteration of run(), which can be called many times in walk.js.
This grew the argument list. The extra args are ultimately ignored, but
this small fix prevents non-parsed arg pollution (i.e. the values nopt
returns in the parsed.remain property).