fix(nextjs): Use webpack module paths to attempt to resolve internal request async storage module #9100
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Attempts to fix #9092
I could never reproduce that issue but my suspicion for that error is that somewhere in the node module resolution tree there is a nextjs installation which will make
next/dist/client/components/request-async-storageresolve.We probably need to limit the module resolution search by what webpack itself is looking for. We can do this by looking at
webpackConfig.resolve.moduleswhich contains all the resolution paths.This is not a 100% probability fix but something that is worth trying.