-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Cannot add @angular/material to new Nx workspace #13377
Comments
Can you try the following:
|
Hi @Coly010 that seems to work with the There is an issue open on the |
@maartentibau yeah I created the PR to add support for angular 15 to jest-preset-angular and it was merged a few days ago thymikee/jest-preset-angular#1840 I believe the maintainer has a few extra things he wants to do before releasing a new version |
Hi @maartentibau @Coly010 `TypeError: Cannot read properties of undefined (reading 'kind')
|
Hi @maartentibau |
@HARIPRASADHARI It looks like you're now encountering a bug from Angular: angular/components#26540 Until they resolve that, there isn't much we can do to help unless you upgrade your TS version to 4.9.5 |
Hi @Coly010, |
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. |
Current Behavior
Create a new Nx Angular workspace (Integrated Repo option)
v15.2.1
.After doing that I wanted to run
npx nx add @angular/material --project=mr-20221129 --verbose
But no matter what I do, nothing will work and I'm always getting the same error.
I really don't understand what I'm doing wrong here.
Expected Behavior
I would think this should work out of the box since Nx uses the Angular CLI
Github Repo
No response
Steps to Reproduce
npx create-nx-workspace@latest
@angular/material
packagenpx nx add @angular/material --project:my-project --verbose
npx nx add @angular/material:ng-add --project:my-project --verbose
npx ng add @angular/material --project:my-project --verbose
Nx Report
Failure Logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: