fix: throw err when supplied config is absent#1760
Merged
alexander-akait merged 4 commits intowebpack:nextfrom Aug 20, 2020
Merged
fix: throw err when supplied config is absent#1760alexander-akait merged 4 commits intowebpack:nextfrom
alexander-akait merged 4 commits intowebpack:nextfrom
Conversation
Member
evenstensberg
left a comment
evenstensberg
left a comment
There was a problem hiding this comment.
Remove the processingMessageBuffer when you're at it
Member
Author
|
Yeah we should get rid of all instances, unused |
Member
Author
|
Done @evenstensberg 💯 |
evenstensberg
approved these changes
Aug 19, 2020
alexander-akait
approved these changes
Aug 19, 2020
Member
|
Good job! |
rishabh3112
approved these changes
Aug 19, 2020
snitin315
approved these changes
Aug 20, 2020
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
6 participants
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.
What kind of change does this PR introduce?
fix
Did you add tests for your changes?
Yes
If relevant, did you update the documentation?
Should we state this somewhere?
Summary
Does this PR introduce a breaking change?
No
Other information
Fixes #1759