@ember/addon-blueprint

Blueprint for scaffolding ember v2 addons

For migrating a v1 addon to a v2 addon, you may follow Porting Addons to V2 and this blog post Migrating an Ember addon to the next-gen v2 format .

Note

This is not yet the default blueprint. For discussion on strategy around this becoming the default, see the RFC

Usage

pnpm dlx ember-cli@latest addon my-addon -b @ember/addon-blueprint --pnpm

Options

For all these options, you'll see a warning printed from ember-cli about unsupported options. ember-cli doesn't have a way to detect if flags are used by a blueprint.

--pnpm

Sets up the new addon with pnpm as a default package manager.

Example:

npx ember-cli@latest addon my-addon -b @ember/addon-blueprint --pnpm
cd my-addon

--npm

Sets up the new addon with npm as a default.

Example:

npx ember-cli@latest addon my-addon -b @ember/addon-blueprint --npm
cd my-addon

--typescript

Sets up the new addon with typescript support.

Example:

npx ember-cli@latest addon my-addon -b @ember/addon-blueprint --typescript

Updating the addon

The blueprint supports ember-cli-update to update your addon with any changes that occurred in the blueprint since you created the addon. So to update your addons boilerplate, simply run ember-cli-update (or npx ember-cli-update if you haven't installed it globally).

For additional instructions, please consult its documentation.

License

This project is licensed under the MIT License.