core: replace WebInspector traceparser with native JSON.parse #6099
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.
possibly more controversial than #6090 and #6091
The reason we introduced a streaming trace parser was because we would get
RangeError: Invalid string length
with traces that were larger than 256MB, the previous maximum string size in V8.This changed in V8 6.2, which increased the max size to 1GB. This landed in Node 8.10.0 in March, which is after the original LTS release of 8.9. However:
-A
mode after core(driver): deliver trace as events rather than a stream #6056It thus seems reasonable to expect at least Node 8.10 to run Lighthouse if we're supporting at least the LTS branch. I've updated the
package.json
engines
entry to give a warning on install innpm
(not sure what the yarnengines
behavior is these days).