mirage enabled even when using `--proxy` flag about ember-cli-mirage

[Techn1x]

Thanks so much! You do great work! I am just glad to see things moving in mirage land :)

[ijlee2]

@Techn1x @SergeAstapov I appreciate the report and the quick response, as my team encountered a related issue on 3.0.0. Updating ember-cli-mirage to 3.0.1 fixed our problem, and the update from 2.4.0 to 3.0.0 went otherwise smoothly. ✨

Even after updating to 3.0.1, one of our developers found that the issue exists on their Windows machine. By temporarily updating the Mirage config to passthrough all requests, the requests to the desired server worked:

function routes() {
  this.passthrough();
  // removed all other overrides
}

We're not sure yet if the Windows issue is an existing one, either in ember-cli-mirage or miragejs. If we can come up with a minimal reproducible app (I imagine this will take time, as we would need to create an Ember app as well as a Rails/Node server), we'll let you know.

(Could be hard-coded / in paths like https://github.com/miragejs/ember-cli-mirage/pull/2559/files#diff-77d6e2aab53cbf594475ecab6eac3882cd95a1c3d95085833caa58c39cb0a910R14.)

[SergeAstapov]

@ijlee2 thank you for the pull request! This is released as v3.0.2

[Techn1x]

cc @deepfryed

[SergeAstapov]

@Techn1x sorry for churn, fix published in v3.0.1