getSize() throws errors if no module.buildInfo #13707
Closed
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
Building my project, I can see that sometimes a module has no buildInfo. In this case, it would be better to also return a size = 0 than to throw an error. I currently experience these errors a lot, which disappear with this simple fix: >> [...]/node_modules/webpack/lib/json/JsonGenerator.js:119 >> let data = module.buildInfo.jsonData; >> ^ >> TypeError: Cannot read property 'jsonData' of undefined
|
For maintainers only:
|
|
fixed by #13708 |
|
@bthorben The most important CI builds failed. This way your PR can't be merged. Please take a look at the CI results from azure (15 errors / 1 warnings) and appveyor (failure) and fix these issues. |
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.
Building my project, I can see that sometimes a module has no buildInfo. In this case, it would be better to also return a size = 0 than to throw an error.
I currently experience these errors a lot, which disappear with this simple fix:
What kind of change does this PR introduce?
Did you add tests for your changes?
Does this PR introduce a breaking change?
What needs to be documented once your changes are merged?