WRP-13739: Fixed ResizeObserver loop limit exceeded
error
#319
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.
Checklist
Issue Resolved / Feature Added
Starting cli 5.1.0 "webpack-dev-server" was updated to latest minor version "^4.9.3". Version 4.12.0 introduced an error that is visible on our console app in agate-apps.
With this version of "webpack-dev-server", at first render or whenever we resize the browser viewport (e.g. by opening developer tools), an error overlay pops up stating "ResizeObserver loop limit exceeded".
This issue is addressed on "webpack-dev-server"'s Github repo: webpack/webpack-dev-server#4771.
The fix for this: webpack/webpack-dev-server#4773. "webpack-dev-server" added this option to show or not runtime errors in an overlay (the default value is true). So if we add
runtimeErrors: false
in cli we do not get theResizeObserver loop limit exceeded
error any more.Resolution
Set
client.overlay.runtimeErrors
tofalse
inserve.js
configuration file to avoid showing errors at window resize.Additional Considerations
Links
WRP-13739
Comments
Enact-DCO-1.0-Signed-off-by: Stanca Pop stanca.pop@lgepartner.com