-
Notifications
You must be signed in to change notification settings - Fork 306
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
[Bug]: Angular 14 support #1410
Comments
Jup. Just update an existing NX project will also get you this error if you go for Angular 14 now. Not sure if there is a workaround for this other than downgrading to angular 13. And I wonder why devkit hasn't been updated yet either. |
You can try this now with |
Thanks for the release, unfortunately I have to report that we are not done yet - not sure what piece in the puzzel is causing the issues but at least I can provide a working angular project: master using branch using on my local machine it feels like a loop and got stucked with super high CPU usage. on the CI there at least some useful warnings and type errors: https://github.com/henryruhs/ngx-crud-playground/runs/6440488572
|
I see the errors above in nx projects only. Pure angular 14 + jest 28 works well. |
Nx doesn’t have official support for Jest 28 yet so please contact them @henryruhs |
Who said that I'm using nx? Check the dependencies... still using |
We have example app which you can try to reproduce your issue https://github.com/thymikee/jest-preset-angular/tree/main/examples Pls don't include any 3rd party tools in your reproduce repo to produce a pure reproduce scenario. Also I noticed that We now also have Angular 14 example app at https://github.com/thymikee/jest-preset-angular/tree/main/examples/example-app-v14 |
Ah, then the Nest command should help: npm update --depth 999 jest-environment-jsdom |
In my case the blocker is |
@satanTime A temporary solution could be |
Hi. My bad. It's not because of types. It's because of nx/jest. It locks some jest packets on 27 and it breaks everything. Force flag doesn't help with it. |
For those who need a temporary solution for Angular 14 - I just found it... so the setup file is causing a loop for some reason, the workaround is an empty one. So this is my current setup of ngx-crud-playground as of 03.07.2022: .npmrc
jest.config.js
jest.setup.ts
|
I am sorry, but I still cannot get this resolved, even after
Here are all my dependencies from my package.json "dependencies": {
"@angular/animations": "^14.1.2",
"@angular/cdk": "^14.1.1",
"@angular/common": "^14.1.2",
"@angular/compiler": "^14.1.2",
"@angular/core": "^14.1.2",
"@angular/forms": "^14.1.2",
"@angular/material": "^14.1.1",
"@angular/material-moment-adapter": "^14.1.1",
"@angular/platform-browser": "^14.1.2",
"@angular/platform-browser-dynamic": "^14.1.2",
"@angular/router": "^14.1.2",
"@material/layout-grid": "^14.0.0",
"ag-charts-angular": "^6.1.0",
"ag-charts-community": "^6.1.0",
"ag-grid-angular": "^28.1.0",
"ag-grid-community": "^28.1.0",
"ag-grid-enterprise": "^28.1.0",
"d3": "7.6.1",
"d3-org-chart": "2.6.0",
"file-saver": "^2.0.5",
"lodash-es": "^4.17.21",
"material-design-icons": "^3.0.1",
"moment": "^2.29.4",
"moment-timezone": "^0.5.34",
"ng-let": "^14.0.1",
"ngx-logger": "^5.0.11",
"reconnecting-eventsource": "^1.5.1",
"rxjs": "^7.5.6",
"tslib": "^2.4.0",
"xlsx": "^0.18.5",
"zone.js": "~0.11.7"
},
"devDependencies": {
"@angular-builders/jest": "^14.0.0",
"@angular-devkit/build-angular": "^14.1.2",
"@angular-eslint/builder": "^14.0.2",
"@angular-eslint/eslint-plugin": "^14.0.2",
"@angular-eslint/eslint-plugin-template": "^14.0.2",
"@angular-eslint/schematics": "^14.0.2",
"@angular-eslint/template-parser": "^14.0.2",
"@angular/cli": "^14.1.2",
"@angular/compiler-cli": "^14.1.2",
"@babel/core": "^7.18.10",
"@compodoc/compodoc": "^1.1.11",
"@openapitools/openapi-generator-cli": "^2.3.0",
"@types/d3": "^7.1.0",
"@types/d3-org-chart": "^2.6.1",
"@types/file-saver": "^2.0.5",
"@types/jasmine": "~4.0.3",
"@types/jest": "^28.1.6",
"@types/lodash-es": "^4.17.6",
"@types/node": "^18.7.1",
"@types/uuid": "^8.3.4",
"@typescript-eslint/eslint-plugin": "5.33.0",
"@typescript-eslint/parser": "5.33.0",
"babel-loader": "^8.2.5",
"eslint": "^8.21.0",
"eslint-plugin-import": "^2.26.0",
"eslint-plugin-jsdoc": "^39.3.6",
"eslint-plugin-no-unsanitized": "^4.0.1",
"eslint-plugin-prefer-arrow": "^1.2.3",
"eslint-plugin-rxjs": "^5.0.2",
"eslint-plugin-rxjs-angular": "^2.0.0",
"eslint-plugin-security": "^1.5.0",
"husky": "^4.3.6",
"jasmine-core": "~4.3.0",
"jasmine-spec-reporter": "~7.0.0",
"jest": "^28.1.3",
"jest-canvas-mock": "^2.4.0",
"jest-junit": "^14.0.0",
"jest-preset-angular": "^12.2.0",
"lodash": "^4.17.21",
"prepush-if-changed": "^1.0.8",
"rimraf": "^3.0.2",
"ts-jest": "^28.0.7",
"ts-node": "~10.9.1",
"typescript": "~4.7.4"
} Output from
What did I do wrong? :( |
You are using |
Hello @ahnpnl, many thanks for your quick reaction. I am not super-experienced with npm, but does the message
Not imply, that @angular-builders is referencing for any Jest version >= 28? How could I resolve this? I tried to downgrade jest (+ types etc.) to v27, but now npm complains again:
Is there any working combination for Angular 14 which I should use? |
|
Don't get me wrong but this is not stackoverflow. The issues has been resolved, if you have problems - this is not the right place. |
@ahnpnl, thank you. I thought, I did exactly that (upgrade to jest 28, see package.json). So, forget it for now, maybe it's a npm-internal problem, many thanks nevertheless. Update: Got it resolved by manually deleting package-lock.json + node_modules. |
Version
11
Steps to reproduce
Create brandnew Angular project via
ng new
with--next
flag.Expected behavior
Nothing to report here...
Actual behavior
At this point there is a dependency conflict:
Additional context
No response
Environment
The text was updated successfully, but these errors were encountered: