chore: Change hint for unresolved dependency. #2808
+49
−49
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.
I had a case where a dev hit a run-of-the-mill resolution failure and blindly followed the hint's instructions, which does read a bit like a "just do this and your problems will be solved!" notice.
Specifying when you may want to exclude a module from a bundle, and what the implications are, hopefully will be a bit easier on the uninitiated and prevent some unintended footguns.