-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can Jest and related packages in the dependencies be upgrades to vesion 29.x.x? #298
Comments
Is there any chance that this can be prioritized please as now update to Jest 29+ is important due to an important fix for NodeJS memory leek (see https://jestjs.io/docs/29.0/configuration/#workeridlememorylimit-numberstring)? |
Hey everyone! Could you please try this version out and provide feedback? It upgrades all dependencies to Jest 29:
|
Testing my project with 60 component tests, everything is good. No errors. |
Works great for my project (1000+ tests), with no errors. |
can these dependencies just be set as peerDependencies? Most of the time users will already be using jest for other purposes and as long as we're compatible we don't have to gum up yarn locks or cause potential conflicts. |
@piratetaco that's a great question, and sorry to hear you're having troubles because of this! We chose to set Jest as a direct dependency for a few reasons:
|
Hey everyone! I'm happy to say that the test-runner now uses Jest 29, please try its beta version here: It will be promoted to latest once it has enough feedback regarding its stability. Thank you! <3 |
Currently, these are outdated and prevent upgrades on the projects that use
@storybook/test-runner
because of incompatible Jest typescript types.The text was updated successfully, but these errors were encountered: