feature: allow for custom error messaging in ModuleScopePlugin #11978
Conversation
This file contains 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
This is purely related to facebook#11977 as a proof of concept for what I'm proposing. It would allow folks who directly use this webpack plugin to customize the error output. Broader use of this error through other means in CRA would need more development.
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.
This is purely related to #11977 as a proof of concept for what I'm proposing. It would allow folks who directly use this webpack plugin to customize the error output. Broader use of this error through other means in CRA would need more development.
This change allows the developer to pass in an error message so that they can provide a custom error message for the missing module in the event that it is ejected from CRA OR when the developer is using
react-dev-utilsdirectly for their own use case (which is my current way of using this). So this allows developers who use this to get a more fine grain result for their end users with a better error message.