-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Jest version 29 is not supported #19
Comments
I see that this ticket is related to comments in issue 17. I would also need this version bump before I could use jest-chrome for my own testing. |
Depending on how you are using {
"devDependencies": {
"jest": "^29.3.1",
"jest-chrome": "^0.8.0"
},
"overrides": {
"jest-chrome": {
"jest": "$jest"
}
}
} |
@nothingrandom If this is working for you, we could probably remove the peer dep from jest-chrome's Thoughts? |
@jacksteamdev I'm fairly sure that you could safely do that. I'm running it through 330 odd unit tests I've got for an extension and nothing broke on my override change or with the jest "core" upgrade. You might find that there is a minimum jest version required, but I don't know if version locking it is the best way to be dealing with that? |
@jacksteamdev looks like you need to cut a release to make this supported for most users. |
@jacksteamdev can you cut a release for this? |
@jacksteamdev Can you please cut a new release for this? |
@jacksteamdev also bumping for a release |
Google search terms
jest-chrome is not work for jest 29
Describe the bug
I have jest 29.3.1 and i try to use jest-chrome to test my browser extension https://github.com/translate-tools/linguist
But i can't even install jest-chrome, because its
packages.json
requires a jest versionjest@"^26.0.1 || ^27.0.0"
How do we reproduce?
npm i -D jest@29.3.1
npm i -D jest-chrome
Expected behavior
Packages installed successfully
Actual behavior
We got an error about incompatible versions
Screenshots
Please complete the following information:
Additional context
The text was updated successfully, but these errors were encountered: