It looks like this PR #2495 released 2 weeks ago under 3.0.0-alpha.4 has removed the config/environment.js file
That config/environment.js file had a usingProxy() function that would set ENV['ember-cli-mirage'].usingProxy to true if proxy flag was set
https://github.com/miragejs/ember-cli-mirage/pull/2495/files#diff-77d6e2aab53cbf594475ecab6eac3882cd95a1c3d95085833caa58c39cb0a910L4-L11
When usingProxy is true, that would disable mirage server in the initializer
|
let usingInDev = env === 'development' && !addonConfig.usingProxy; |
Right now nothing sets that usingProxy property in the config, so mirage ends up being enabled even when proxies are set
This seems like an unintentional change (wasn't mentioned in 3.0.0 Breaking Changes)
It looks like this PR #2495 released 2 weeks ago under 3.0.0-alpha.4 has removed the
config/environment.jsfileThat
config/environment.jsfile had ausingProxy()function that would setENV['ember-cli-mirage'].usingProxyto true if proxy flag was sethttps://github.com/miragejs/ember-cli-mirage/pull/2495/files#diff-77d6e2aab53cbf594475ecab6eac3882cd95a1c3d95085833caa58c39cb0a910L4-L11
When
usingProxyis true, that would disable mirage server in the initializerember-cli-mirage/packages/ember-cli-mirage/app/initializers/ember-cli-mirage.js
Line 54 in dc38525
Right now nothing sets that
usingProxyproperty in the config, so mirage ends up being enabled even when proxies are setThis seems like an unintentional change (wasn't mentioned in 3.0.0 Breaking Changes)