-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: CLI to automate import from "@jest/globals" #14767
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This is a feature request. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This is a feature request. |
Finally I found a solution, thanks to the awesome tool @getgrit! |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
馃殌 Feature Proposal
It would be nice to have some helper to automate the migration from v28 to v29, mainly to add
import {} from '@jest/globals'
explicitly on +500 files per project.Motivation
Changing +500 files on 4 projects manually it's a pain that would be great to avoid.
Example
No response
Pitch
My suggestion is to provide some CLI or external tool to help in the migration process.
The text was updated successfully, but these errors were encountered: