Fix compatibility with latest Puppeteer version #566
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
Puppeteer recently changed the naming of their classes in puppeteer/puppeteer#10903, which caused the case-sensitive class name checks in `expect-puppeteer` to fail.
|
@gregberge Prettier issues are now addressed |
|
Will take care of it soon. |
|
@swissspidy tests are all broken |
|
I can confirm this fixed my issue. Thank you! |
|
Thank you! |
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.
Summary
Puppeteer recently changed the naming of their classes in puppeteer/puppeteer#10903, which caused the case-sensitive class name checks in
expect-puppeteerto fail.Fixes #565
Test plan