Ember.js support

[mike-north]

I've spoken with many leaders in the Ember.js core team/community and we love StackBlitz as a tool. We maintain ember-twiddle which aims for similar goals, but it's much less refined for a variety of reasons (i.e., VScode/Monaco were not yet public at the time it was built, service workers were highly experimental, and we cared a lot about IE10/11).

We're now faced with the choice of either facilitating support for Ember projects in some already-existing "playground" app like Stackblitz, or building/fixing something similar that just works with ember-cli apps. In this case, I have a strong preference for contributing to your project rather than building/maintaining a seperate (similar) thing.

is there some way we can work together to add Ember support to stackblitz? If you were were handed a piece of worker-friendly code that, in a single async function call, converted source code into browser-ready output -- would the remaining work on your end be relatively easy?

[jmonster]

disappointed to see that this issue has been ignored; @mike-north did you pursue an alternative? I've been looking for the best way to do ember+node from an iPad, VS Code being preferred, wound up here..

[mike-north]

After waiting for a few months on this issue, I added Ember.js support to https://codesandbox.io/

[Alonski]

Would still love for this to be implemented

[jamescdavis]

I would love to see this. Maybe, with WebContainers, there's a path to making it a reality?

[NullVoxPopuli]

I think we're waiting on this: stackblitz/webcontainer-core#53

[gnclmorais]

So… are we any closer to this? 🤞

[NullVoxPopuli]

I'd say so. Most of what happens when I play with stackblitz seem to be minor state related bugs. Like,:

• telling me to get a pro account for no reason
• not saving files due to every file being saved in one post request -- saving should be per changed file
• not detecting what port the dev server is on (requires refresh to fix)

I haven't yet tried to see if the generated static assets are available to other people after I'm done editing.

[fvsch]

Hi everyone!

I’ll close this as a duplicate of stackblitz/webcontainer-core#354 which has a bit more information about Ember.js support in WebContainers. It seems we're currently blocked by usage of the esm package that conflicts with our own ESM loader code.

Solutions might include:

• The Ember.js project moving away from the esm shim.
• Us finding a way to make the esm package work in WebContainers (no work on that on our roadmap as far as I know, but never say never ^^).