Improve Puppeteer's trimCache
API usage
#16519
Merged
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.
The original
trimCache
functionality was intended to be exposed on the top-levelpuppeteer
module, but due to a bug in Puppeteer this didn't work correctly and we had to calltrimCache
on the default Puppeteer node instance instead, which was fortunately exposed. However, since this didn't feel like intended API usage, this bug was reported and is now fixed in Puppeteer 20.5.0, so this commits updates Puppeteer to that version so we can use the intended API.The full history of this issue can be found at puppeteer/puppeteer#10174.