Upgrade jest and related packages from 26.6.0 to 27.1.0 #11338
Conversation
|
Hi @krreet! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
|
This looks great. Can you revert the changes to |
|
Hi @iansu |
|
Not sure why we should need to check-in package-lock.json - feels wrong... @iansu we do sometimes have to run the 'yarn compile:lockfile' for tests to pass |
* Upgrade jest and related packages from 26.6.0 to 27.1.0 * adds the latest yarn.lock.cached file * runs yarn compile:lockfile * resolve conflicts with the main branch * adds the package-lock : npm ci with npm7 * adds the package-lock : npm ci with npm7 * Revert yarn.lock.cached * update postcss-normalize to 10.0.1 to resolve smoke test failures Co-authored-by: reetkr <reetesh.kumar@blazeclan.com>
Closes #10747. Fixes #9993.
Tested and working fine with jest 27.1.0
yarn test , yarn start , yarn build
included changes from #10748