@jorblume wrote:
Problem space:
Running two different Ember applications that require two different ember versions causes issues. Since the new ember cli vendor js is loaded last, the old application is now hitting the new Ember library, and causing all sorts of problems. I believe this is because the last loaded Ember library overwrites the window.Ember object and the old application is calling window.Ember.sometfunctionhere.
Both applications and associated js end up on the page in separate, non-nested divs. The old application is a 2.5.x version, but the new version is ahead enough that I am getting deprecation warnings.
I would like to make sure the old application only uses its old library, while the new ember application only uses its new vendor file.
I was wondering if anyone had any bright ideas on how to accomplish this. Ideally I would be able to have the new application bind to a new custom window namespace, or some kind of “no conflict” mode for the new application to avoid messing with the old one.
Solutions:
- iFrame the new application, but this poses another host of issues related to iframes.
- Attempt to fix the old application and deprecation problems, but possibly introduce new issues or problems.
Posts: 1
Participants: 1