Closed sklawren closed 2 years ago
I'm actually wondering: why do you need this package to update its devDependencies
? These dependencies should not impact the package users.
jest-fail-on-console
actually has no dependency nor peer dependency on Jest so it should not impact your Jest 28 update.
For some reason, I was getting complaints from npm about dependency clashes but they seemed to have disappeared now that I tried it again.
I updated Jest on one of my projects yesterday and there was no issue related to this package. I'll probably update Jest on this package but I will not do a major version update as dev dependencies should not impact it.
Closing as we couldn't confirm there was a real issue linked to this package. Please comment if need to reopen.
Please do a major version (semver) update to set devDependencies to Jest 28.