Yup, I agree with @RGJ. Based on the ‘Ember not found’ error mentioned above, the most likely issue is the ‘ember-global’ deprecation. More details on that here (linked from the original announcement). In these plugins, it looks like that’s being used for Ember.Component, and also for some Ember.computed.* calls.
Here are a couple of quick PRs. It’s possible there are other issues which will reveal themselves after this fix is made, but I don’t see anything obvious skimming through the JS code.
Thanks for the feedback on the rollout process! We’re constantly working to strike the right balance between progress and stability. We’ll definitely be taking what we’ve learned from this rollout and apply it to future upgrade/refactoring projects.