Correct process for upgrading an Ember-cli addon

Question

What is the correct process for upgrading an Ember-cli addon? If I follow the normal process for upgrading an ember app:

npm uninstall -g ember-cli
npm cache clean
bower cache clean
npm install -g [email protected]
rm -rf node_modules bower_components dist tmp
ember install:npm [email protected]
ember install
ember init

It will replace the brocfile with ember-app instead of ember-addon. Will this let it still work as an addon?

I assume you mean this line at the top of the Brocfile? var EmberAddon = require('ember-cli/lib/broccoli/ember-addon'); The addon blueprint still has that content in the Brocfile so it sounds like ember-cli doesn't know it's in an addon directory. Does your addon have have "keywords": ["ember-addon"] in the package.json file? — steveax

robdel12 robdel12 · Accepted Answer · 2015-03-24T19:31:39

It looks like this has been taken care of in Ember-cli master. Mr. Penner says he's trying to get Ember CLI 0.2.2 out the door. That should fix your issue.

Edit: I can confirm 0.2.2 will fix this. Just pulled Ember-cli master and ran an update on one of my addons.

Correct process for upgrading an Ember-cli addon

1 Answers