deps: upgrade puppeteer to 22.11.1 #16070
Merged
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
connorjclark
approved these changes
Jun 17, 2024
adamraine
changed the title
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.
https://github.com/puppeteer/puppeteer/releases/tag/puppeteer-core-v22.11.1
https://github.com/puppeteer/puppeteer/releases/tag/puppeteer-core-v22.11.0
https://github.com/puppeteer/puppeteer/releases/tag/puppeteer-core-v22.10.1
There were some type errors that appeared only because we reach into pptr internals for Lightrider entry. I didn't see a way to hack around it so I went with what I think is a better way to handle this situation: just use
skipLibCheckin a new tsconfig.json.This also removes the need for that stupidNevermind we do need it 馃檭rxjs.d.tshack introduced a while back.