Georg Kothmeier

We came across the same problem luckily @mnunmununm from the discord channel pointed us to this issue. Hopefully, it can be resolved someday because it's not a good developer experience...

@chriskrycho you mean the https://typed-ember.github.io/ember-cli-typescript/versions/master/docs/ts-guide/current-limitations section? I could write something explaining this issue. Or maybe it's enough to just link here. To be honest, I was quite lost today and...

I create a repo which should demonstrate the issue, see here: https://github.com/tschoartschi/mirage-passthrough-wasm The WebAssembly module should print "hello world" to the browsers dev tools console. When Mirage is active but...

Please just let me quickly know if you are able to reproduce the issue 🙂 if not I could try to provide further information. Thanks a lot

@samselikoff no worries 🙂 I created a repo about two weeks ago, see: https://github.com/miragejs/miragejs/issues/339#issuecomment-596625395 Thanks for your great work and let me know if you need anything else

Yesterday I had time to dig into this problem a little more. I think we are facing two issues here: - the same problem as in (https://github.com/miragejs/ember-cli-mirage/issues/1915). Which basically is...

I found a workaround which works at least for us, what I do now is the following: ```JavaScript new Server({ environment: 'development', logging: true, routes() { // Needed because Chrome...

For everyone who followed this issue, I needed to update the snippet from above slightly. I needed to save the old `passthroughRequest` to a variable so I can call it...

@samselikoff since we found workarounds for the problems stated above I tried to follow the Cypress Quick Start guide (https://miragejs.com/quickstarts/cypress/) but now I have again problems with the binary files...

If someone reads along with this issue I found a workaround which works for us 🙂 basically what we are doing now is the following: ```typescript import {Server, RestSerializer, Response...