-
Notifications
You must be signed in to change notification settings - Fork 313
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
fix(jest): update cache function for new Jest 27 API #408
Conversation
An alternative would be to use https://github.com/facebook/jest/tree/e5816610eaa6d8aa6b4742909d7495be77f8f347/packages/jest-create-cache-key-function which will handle both 26 and 27 version of the signature |
This change is required to use the |
Any news on when this will be merged? |
This would be great to have merged! |
If anyone is here because they're using react-native -- you can use yarn resolutions as described here
|
I also have this issue after upgrading to Jest 27. I'm up to date on React Native as well. |
Same here. Jest 27 breaks my project's CI 😅 though I'll add this curious tidbit: for whatever reason, it actually runs properly locally (macOS 11.4), but specifically fails when run this very simple Github workflow based on name: Node.js CI
on:
push:
branches: [master]
pull_request:
branches: [master]
jobs:
build:
runs-on: ubuntu-latest
strategy:
matrix:
node-version: [14.x]
# See supported Node.js release schedule at https://nodejs.org/en/about/releases/
steps:
- uses: actions/checkout@v2
- name: Use Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v1
with:
node-version: ${{ matrix.node-version }}
- run: npm ci
- run: npm run lint
- run: npm test |
Tagging the latest releaser @GijsWeterings |
Getting this merged would be excellent. Breaking us too on a Jest 27 upgrade attempt. |
LGTM :) |
See jestjs/jest#10834