Upgrading to new versions of Ember

@mehulkar wrote:

After years of Ember development, it seems I’m still confused about the recommended way to upgrade Ember. My main confusion is about compatibility between the different line items in package.json. I don’t use ember-data, so I really just care about updating ember-source. But since a default Ember CLI app has a few other packages, it’s unclear what I need to update.

I’ve tried ember-cli-update, but without reading the source code, it’s not really clear what it does. At this point in time, I tried updating to 3.11 and discovered that it doesn’t check for available updates of ember-source, it checks for available updates of ember-cli! This was kind of unexpected, but I’m assuming that after upgrading ember-cli, it goes and overlays the default ember new blueprint and expects the user to resolve conflicts and then run npm install?. Because of this confusion, it doesn’t really seem like a viable solution.

Starting this post to hear from other’s experience upgrading Ember.js and how they go about it. Maybe the right solution is to really consider every line item in package.json individually, just like I would with any other Node app, and resolve incompatibilities as they arise?

Posts: 2

Participants: 2

Read full topic