-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The requested module 'ts-auto-mock' does not provide an export named 'createMock' #1453
Comments
Hey, I've looked into this a while ago and I couldn't figure it out yet! Happy to see a PR for the changes required to the build process! |
This is a weird interaction with the "named" exports becoming the default import. import { createMock } from 'ts-auto-mock'; it needs to be import autoMock from 'ts-auto-mock';
const { createMock } = autoMock; Looking into how the index.js file can be patched to fix this. This also happens regardless of whether the transformer ran successfully or not, since it does not remove these "fake" imports. |
It looks like the current compiled code does module.exports = { createMock: ... } And it needs to do module.exports.createMock = ...;
|
Here's a yarn patch file that fixes both this & #1094 |
Subject of the issue
When used in a Jest ESM environment, attempting to import
createMock
results in a error:Your environment
Steps to reproduce
Reproducible example available here. Project is set up in accordance to the Jest ESM docs.
Expected behavior
ts-auto-mock
should work fine in ESM environments.Actual behavior
ts-auto-mock
doesn't work in ESM environments as importing it results in an error.The text was updated successfully, but these errors were encountered: