/ jest Public
fix(@jest/resolve): Include stringifiedOptions in getModuleIDAsync #12766
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge.
I use native ESM with the
--experimental-vm-modulesflag. When upgrading to Jest 28,
I tracked this down to the mock detection failing due to
getModuleIDAsyncnot generating identical IDs. In this case
getModuleIDAsyncdid not append the stringified options, so the lookup using the ID as a key failed.
There are other slight differences between
getModuleIDAsyncthat might lead to similar issues.
jest.unstable_mockModulefollowed by a dynamic import should resolve the mocked module