fix(testing): puppeteer v10 support #2939
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.
Important Front Matter
This PR is a port of #2934, which has largely already been reviewed:
The 'new stuff' includes:
Pull request checklist
Please check if your PR fulfills the following requirements:
npm run build
) was run locallyand any changes were pushedPull request type
Please check the type of change your PR introduces:
What is the current behavior?
In this PR, we upgrade Stencil to allow support for v10.0.0 of Puppeteer. The version of Puppeteer (v5.5.0) supported in
stencil@2.6.0
has two separate issues:npm install
cannot be easily run in the Stencil repo itself on newer Mac machines (those using an M1). This was fixed on the Puppeteer side in feat(launcher): fix installation error on Apple M1 chips puppeteer/puppeteer#7099What is the new behavior?
@types/puppeteer
Does this introduce a breaking change?
Manual Testing
npm build
andnpm pack
from the root of the repo directory (on this branch)npm init stencil
npm t
in my stencil app passedOther information