-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Ember to the framework options on create-single-app #268
Comments
There isn't a lot of ember expertise in the single-spa core team, so this one might be tricky. In the past, Ember has been a bit tricky to support. @rajasegar has done a fair amount of work for supporting Ember, though, including this example. Perhaps he could help guide what ember support in create-single-spa would look like |
@PazAutumn Ember is really not a conducive framework for creating Micro-Frontends because of a lot of reasons. The main one being the usage of a lot of global variables for storing app context like window.Ember, loader, require, define and so on. Having been working on this for a long time I came to this conclusion and I am pushing to move away from Ember at work to a more Micro-Frontend friendly frameworks like React, Vue, etc., I link some of the resources likes blog posts, examples and issues I have been dealing with Ember and single-spa in the past so that some one who is treading down the same road as me will move in the right direction: Hence I stand with the single-spa team on this matter, until the Ember team come up with a solution to have multiple Ember apps coexist in the browser without using any hacks or iframes. So adding Ember to create-single-spa is not worth the effort. |
Thank you @rajasegar for your arguments, you gave me a lot to think of. |
I'm looking forward to use single-spa but my main project uses ember and is not in the options, it would be nice to add it for making the process more easy. thank you!
The text was updated successfully, but these errors were encountered: