setupMirage under embroider? about ember-cli-mirage HOT 3 CLOSED

The link you refer to still uses setupMirage, the code it refers to is how mirage/config.js should now be formatted.

Still learning embroider and trying to figure it out. Importing setupMirage should work the same as importing anything else from test support for any other addon. Embroider should see the import and include the code.

I am looking at ember-qunit and dont see a difference in how they configure and export setupApplicationTest vs how we are exporting setupMirage.

When you say you are using embroider, what exactly does that mean? You are setting the more stricter modes?

from ember-cli-mirage.

@SergeAstapov This looks like another import that should be deprecated.

import { setupMirage } from 'ember-cli-mirage/test-support';

is the way it should be done. I didnt notice in your original post that you stated that. Not sure I would have noticed and it should have worked. But still learning how embroider works so good to know.

from ember-cli-mirage.

Okay thanks for the tip, I'm using embroider with the "Optimized Safe" flags.
I looked at my imports again and was able to make it work by changing it from:

import setupMirage from 'ember-cli-mirage/test-support/setup-mirage';

to

import { setupMirage } from 'ember-cli-mirage/test-support';

My IDE tells me both imports are valid but embroider/webpack wasn't able to import the package the old way when embroider was added to the build pipeline.

from ember-cli-mirage.