docs(testing): add explicit mention of testing lib versions #804
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
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/ionic/stencil-site/GR5xus7Nxp7cuYCvMBXHZuXD97XU |
14 tasks
state the versions of jest and puppeteer that are supported by stencil
rwaskiewicz
force-pushed
the
jest-27-n-at
branch
from
489239d
to
6744a07
Compare
ltm
approved these changes
Jan 5, 2022
|
This is great. We'll certainly take another pass at it as part of our docs campaign, but I really like the improvements here. |
a-giuliano
approved these changes
Jan 5, 2022
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.
Changes
state the versions of jest and puppeteer that are supported by stencil. this is the 'required' work for supporting Jest 27+. however, i took an initial stab at some rework of the testing overview page, but by no means is it "good enough" for us to mark it off our sheet of pages we want to improve. the test configuration & IDE integration could certainly use a little more love, but I think it's in a slightly better state than where it was/is today