New Angular Material schematics directory appears in project's root folder
See original GitHub issueBug, feature request, or proposal:
Bug
What is the expected behavior?
There seems to be a new Angular Material schematics directory in my project’s root folder after updating to 6.0.0
. This directory shouldn’t exist.
What is the current behavior?
The directory exists after updating.
Note the angular_material_schematics_cDdroP
directory in the output of ls
:
What are the steps to reproduce?
- Have an existing project.
- Update that project to
6.0.0
.
What is the use-case or motivation for changing an existing behavior?
NIL
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
- Angular 6
- Angular Material 6
- All operating systems
- TypeScript
2.7.2
- All browsers
Is there anything else we should know?
P.S. The directory seems to be ignored when entering git status
…
P.P.S. Someone else also asked the same thing about this on StackOverflow: https://stackoverflow.com/questions/50178633/angular-material-schematics-folder-after-upgrade-to-angular-6
Issue Analytics
- State:
- Created 5 years ago
- Reactions:16
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Schematics - Angular Material
The tree schematic can be used to quickly generate an Angular component that uses the Angular Material <mat-tree> component to visualize a nested...
Read more >How to access Angular project folder from a custom Angular ...
That being said, here's one way to do it - read in angular.json in your schematic and pull out the sourceRoot attribute for...
Read more >Total Guide To Custom Angular Schematics | by Tomas Trajan
1. Create project. Let's generate new schematics project using schematics blank hello . What we will get is a folder with the following...
Read more >Use Angular Schematics to Simplify Your Life | Okta Developer
In short, it provides an API that allows you to manipulate files and add new dependencies in Angular projects.
Read more >Creating Beautiful Apps with Angular Material - Auth0
create a new Angular project under angular-material-tutorial ng new ... command will move your terminal into the project root directory.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@julianobrasil Just tried what you suggested in updating my other app to Angular v6, but I still encountered the error, even after updating the global and local Angular CLI to
6.0.1
.While updating, I encountered this error after the Angular CLI logged when adding the Angular Material schematics folder:
EDIT: Here’s a full log: https://gist.github.com/Chan4077/ef7e19d7fedb5acd6930a29078205103
Here’s the result from
ls -hFl
:I am facing the same issue as @Chan4077 For the update, I followed the steps provided here.
After updating the CLI (v6.0.1) and Angular Core, I executed
ng update @angular/material
. This first updates @angular/material and @angular/cdk to version 6.0.1. Then it creates all the schematics. After that, I get a lot of errors (TypeError: directiveMetadata.properties is not iterable
) and the command seems to get stuck. I guess, thats why the schematics are not cleaned up, as the command does not finish it’s execution.