Ember CLI Legacy Blueprints

0.2.1 verified Thu Apr 23 auth: no javascript abandoned

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.

Common errors

error Blueprint not found: component ↓

cause This error typically occurs in a project that requires blueprints but `ember-cli-legacy-blueprints` is either not installed or its blueprints are being inadvertently overridden. Alternatively, in a modern setup, it means the core `ember-source` addon is missing.

fix

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.

error The `bower.json` file is no longer required and can be removed. ↓

cause This message indicates that your Ember CLI project has evolved past the need for Bower. `ember-cli-legacy-blueprints` is specifically designed for projects *still using* `bower.json`.

fix

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.

Warnings

breaking This package is specifically designed for Ember CLI projects that still use Bower for managing Ember and Ember Data dependencies. Modern Ember applications manage these core dependencies via npm, and their corresponding blueprints are provided directly by `ember-source`, `ember-data`, and testing framework addons (e.g., `ember-cli-qunit`). Continued reliance on `ember-cli-legacy-blueprints` indicates an outdated project setup that is likely to encounter compatibility and maintenance issues with newer Ember versions or contemporary tooling. ↓

fix 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.

gotcha If modern addons such as `ember-source`, `ember-data`, `ember-cli-qunit`, or `ember-cli-mocha` are also installed in your project alongside `ember-cli-legacy-blueprints`, their blueprints will take precedence and override any identically named blueprints provided by this legacy package. This can lead to unexpected blueprint behavior, outdated code generation, or confusion regarding which blueprint is actually being used. ↓

fix 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.

deprecated The practice of using Bower for managing core Ember and Ember Data dependencies is deprecated within the Ember ecosystem. This addon exists solely to support projects adhering to that legacy dependency management approach. Modern Ember development exclusively utilizes npm or Yarn for dependency management. ↓

fix 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`.

gotcha The `engines` field in `package.json` for `ember-cli-legacy-blueprints` indicates compatibility with very old Node.js versions (`^4.5 || 6.* || >= 7.*`), which are long End-of-Life. While the addon primarily provides static blueprint files, its integration with Ember CLI's internal mechanisms might not be fully compatible with recent Node.js LTS versions, potentially causing installation failures or unexpected behavior during blueprint generation. ↓

fix 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.

Install

npm install ember-cli-legacy-blueprints

yarn add ember-cli-legacy-blueprints

pnpm add ember-cli-legacy-blueprints

Quickstart

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.

ember install ember-cli-legacy-blueprints

# Now you can use the legacy blueprints, for example:
ember generate component my-legacy-component
ember generate route my-legacy-route
ember generate model user-profile