Skip to content
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

Closed
PazAutumn opened this issue Mar 4, 2021 · 3 comments
Closed

Add Ember to the framework options on create-single-app #268

PazAutumn opened this issue Mar 4, 2021 · 3 comments

Comments

@PazAutumn
Copy link

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!

@joeldenning
Copy link
Member

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

@rajasegar
Copy link

rajasegar commented Mar 4, 2021

@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:
ember-cli/loader.js#204
https://github.com/rajasegar/multi-ember-app
ember-cli/ember-resolver#629
https://dev.to/rajasegar/ember-micro-frontends-with-single-spa-1p8j
Having said that we are actually building micro-frontends with multiple Ember apps at work with a lot of hacks like reloading the pages for different Ember apps so that they work properly due to the fact that at any point of time only one Ember app can work properly in the browser unless you put the other one inside an iframe or something. Our microfrontend structure looks like we have 2 React apps and 2 Ember apps but it is not a SPA experience as I said earlier because of the constraints from Ember.

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.

@PazAutumn
Copy link
Author

Thank you @rajasegar for your arguments, you gave me a lot to think of.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants