Getting Started

For an existing app or addon, you first need a starting config to track ember-cli changes.

ember-cli-update bootstrap

This will give you a starting point for future change tracking. It detects your current version of the ember-cli blueprint. After this change, you don't need to worry about updating your ember-cli package version in your package.json, because ember-cli-update now uses the config instead to get the version.

Now if you have any addons with default blueprints that you want to track, you can save their initial state.

ember-cli-update save ember-cli-mirage --from 0.4.15

Now when you run ember-cli-update, you will get a prompt for which blueprint to update.

You can install new addons with their blueprint state stored.

ember-cli-update install ember-cli-deploy

You can also init partial blueprints that sprinkle additional boilerplate on top of your project.

ember-cli-update init -b ember-extra-blueprint
ember-cli-update init -b ember-a11y-blueprint

You will need to resolves the conflicts between this blueprints and what you already have. They might supply a partial index.html file. The tool will attempt to overwrite your index.html with the partial one. It is up to you to resolve the differences by retaining most of your index.html and cherry-picking the changes in the new partial file. You will only have to do this once. Future changes to the blueprint will be targeted to the matching partial sections in your new index.html.

Now when these blueprints are tweaked upstream, you can keep them in sync just like you would with ember-cli or addon changes.

Some of the commands do excess network and disk IO. This is OK for now. Fixing bugs is a bigger priority.