-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 24 and jest-preset-angular 7 changes #1029
Comments
I'm excited for the changes in Jest 24 :) I think we'll wait for |
So what can be done in the meantime? My tests don't run now. I have the same issue as #1054. |
@YonatanKra If you downgrade jest to v23.6.0 it should work |
For some reason it doesn't happen locally - only on circle-ci. I've set the version to just |
This issue is now relevant to https://www.npmjs.com/advisories/786 , not upgrading to Jest >= 24 will report security issues with a dependency (braces) during installations and npm audits. |
thymikee/jest-preset-angular#224 was merged and I tested it with Nx with the changes that @vitalyiegorov mentioned and it's looking good. I'll write the migrations tonight :) |
jest-preset-angular v7 was released. So no more a blocker. |
downgrading is not working. is there any other alternative? |
I still get with version 7.1.1:
|
For those who are still facing this issue, this solution has helped me.* |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
After updating to latest Jest(24.0.0) and jest-angular-preset(7.0.0-alpha.2) which has some breaking changes:
https://github.com/thymikee/jest-preset-angular/blob/release/7/CHANGELOG.md
This is only showing warnings for now but the main problem is that it does not find
tsconfig.spec.json
anymore.Debugging
jest-builder
showed that change in https://github.com/nrwl/nx/blob/7.1.x/packages/builders/src/jest/jest.builder.ts#L47:fixes tests.
Also its weird that I cannot override
globals
Jest settings in myjest.config.js
which I think would be expected.Prerequisites
Expected Behavior
Running jest unit tests normally as was before an update to latest Jest and jest-preset-angular
Current Behavior
It resolves always to monorepo root folder, not to lib folder.
The text was updated successfully, but these errors were encountered: