-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
require.requireActual
returning mock of lodash
in [email protected]
#670
Comments
It's also possible that I'm not understanding what |
This is almost certainly a bug. Can you publish a test repository with a repro for me so I can fix this? |
@cpojer Update, this may be related to #231, taking the demo repo above sterpe/jest--670, and swapping out |
Updated the repro here to include a test with |
require.requireActual
returning mocks in [email protected]
require.requireActual
returning mock of lodash
in [email protected]
Sorry for not getting back to you earlier but this issue should be resolved in jest 0.9.0. I think you might have been using npm3 or deduped some npm2 dependencies because your repro passes just fine for me. See #554 #732 #737 Let me know if this is not fixed when using |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This seems weird but I am seeing
require.requireActual
returning mocks instead of the actualThe work around is to add
"<rootDir>/node_modules/lodash"
tounmockedModulePathPatterns
...but it doesn't feel like that should be necessary...?The text was updated successfully, but these errors were encountered: