Folks wanting to inspect the state of the build pipeline at that stage, would do the following:
BROCCOLI_DEBUG=ember-engines:* ember b
Now you can take a look at the state of that input tree by:
ls DEBUG/ember-engines/*
API
interface BroccoliDebugOptions { /** The label to use for the debug folder. By default, will be placed in `DEBUG/*`. */ label: string /** The base directory to place the input node contents when debugging is enabled. Chooses the default in this order: * `process.env.BROCCOLI_DEBUG_PATH` * `path.join(process.cwd(), 'DEBUG')` */ baseDir: string /** Should the tree be "always on" for debugging? This is akin to `debugger`, its very useful while actively working on a build pipeline, but is likely something you would remove before publishing. */ force?: boolean}class BroccoliDebug { /** Builds a callback function for easily generating `BroccoliDebug` instances