fix: pass resolve conditions when loading stub module#15489
Merged
SimenB merged 9 commits intoFeb 14, 2025
Conversation
✅ Deploy Preview for jestjs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
SimenB
requested changes
Feb 4, 2025
Member
SimenB
left a comment
There was a problem hiding this comment.
thanks, this seems like a good change 👍
In addition to the inline comments, mind adding a changelog entry?
c29e3b7 to
1accf78
Compare
|
This pull request 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 file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.Suggestion cannot be applied right now. Please check back later.
Summary
Problem:
When stubbing the existing
node_modulepackage by anothernode_modulepackage viamoduleNameMappersettings, theresolve conditionsare not respected. For example, in this PR, it does not resolve tobrowserexport of theexample-test-modulewhen the test environment isjsdom.Solution:
Pass through the
options.conditionsfield in theresolveStubModuleName.Test plan
Demonstrated in the unit test