decouple from ember-cli

Nobody has claimed this yet.

Start by reviewing lib/blueprint.js at the listed locations, especially the task loading, blueprint lookup, UI, addon reporting, and ember-cli reference sections. Trace how these areas depend on ember-cli and how task and lookup strategies are supplied. Done means the listed ember-cli, pod, task, UI, reporting, and lookup dependencies have clear external boundaries, with standalone consumers able to provide them.

Written by the indexing model from the issue text.

https://github.com/ember-cli/blueprint/blob/master/lib/blueprint.js#L660
https://github.com/ember-cli/blueprint/blob/master/lib/blueprint.js#L783-L802
provide boundary for abstract tasks taskFor('npm-install)maybe rename tonode_module:install` and external consumer can provide the functionality
- load tasks via what the consumer provides: https://github.com/ember-cli/blueprint/blob/master/lib/blueprint.js#L1107
provide standalone UI abstraction that can be provided, otherwise have ember-cli provide that UI.
load blueprints based on provided lookup strategy:
https://github.com/ember-cli/blueprint/blob/master/lib/blueprint.js#L1479-L1480
in-report addon stuff: https://github.com/ember-cli/blueprint/blob/master/lib/blueprint.js#L435
references to pod
references to ember-cli
- https://github.com/ember-cli/blueprint/blob/1ee765ee6adb9df8bd627f50e53c52c2ba082498/lib/blueprint.js#L27

Assessment

Research direction

Description

Contributor guide

First steps

More from ember-cli/blprnt

Similar issues