The `ember-cli-legacy-blueprints` package (version 0.2.1) is an Ember CLI addon developed to provide backward compatibility for older Ember CLI projects (specifically those targeting Ember CLI 2.0.0 or later) that continue to manage Ember and Ember Data dependencies using Bower.js. It reintroduces a comprehensive set of standard blueprints—such as `component`, `controller`, `route`, `model`, `service`, `adapter`, `serializer`, and `acceptance-test`—which, in contemporary Ember CLI configurations, are bundled directly with their respective library addons (e.g., `ember-source`, `ember-data`, `ember-cli-qunit`). This addon is exclusively relevant for legacy applications that have not yet transitioned their core dependencies from Bower to npm. Its primary function is to ensure that `ember generate` commands operate correctly in these aged environments, thereby preventing errors associated with missing blueprint definitions when utilizing outdated dependency management practices. New Ember projects or those that have successfully migrated their core dependencies to npm should neither require nor install this package.
npm install ember-cli-legacy-blueprintsNo compatibility data collected yet for this library.
Installs the legacy blueprint addon into an Ember CLI project, enabling the generation of components, routes, and other artifacts in older setups that still rely on Bower for dependencies.
Migrate your project's Ember and Ember Data dependencies from Bower to npm. After migration, remove `ember-cli-legacy-blueprints` and install the official Ember, Ember Data, and testing addons as npm dependencies.
Ensure that only the necessary blueprint providers are installed. For modern projects, `ember-cli-legacy-blueprints` should be removed. For legacy projects not yet migrated, avoid installing the newer addons until the migration process is complete.
Update your project's dependency management from Bower to npm/Yarn. This involves removing `bower.json`, updating `package.json` with npm dependencies, and consequently removing `ember-cli-legacy-blueprints`.
For modern Ember development, always use a currently supported Node.js LTS version. For legacy projects that absolutely require this addon, be aware that compatibility issues may arise with newer Node.js versions, and a specific older Node.js version might be necessary for stable operation.
For legacy projects still using Bower, confirm `ember-cli-legacy-blueprints` is installed via `ember install ember-cli-legacy-blueprints`. For modern projects, ensure `ember-source` (and other relevant library addons) are properly installed as npm dependencies.
If you see this message, it's a strong indicator that your project is ready to fully transition away from Bower. Proceed to remove `bower.json` and uninstall `ember-cli-legacy-blueprints`. Ensure all Ember-related dependencies are managed via npm/Yarn.
No dependency data recorded yet.