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.
Upgrade Jest from v27 to v29. We had previously upgraded Jest to v28, but had to downgrade to v27 because at the time,
@storybook/test-runner
only supported up to v27. In v0.7 of@storybook/test-runner
, they changed Jest to be an internal dependency instead of a peer dependency, allowing us to use whatever version of Jest we want.There was only one breaking change in v29 that affected our code, besides those that already needed to be made when upgrading from v27 to v28 (see previous PR description). This was the
jsdom
upgrade from v19 to v20 injest-environment-jsdom
, which requires thetypescript
version to be 4.5 or higher.With the new support added in v29 and
uuid
v9, we are now able to remove the manual resolving needed intests/__setup__/resolver.ts
. For more context on why this was initially needed with Jest v28, see #169.J=SLAP-2376
TEST=manual
See that existing tests still run properly.