_ _ ____ _ ___
/ \ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|
/ â–³ \ | '_ \ / _` | | | | |/ _` | '__| | | | | | |
/ ___ \| | | | (_| | |_| | | (_| | | | |___| |___ | |
/_/ \_\_| |_|\__, |\__,_|_|\__,_|_| \____|_____|___|
|___/
Angular CLI: 6.0.5
Node: 10.1.0
OS: darwin x64
Angular: 6.0.3
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
Package Version
------------------------------------------------------------
@angular-devkit/architect 0.6.5
@angular-devkit/build-angular 0.6.5
@angular-devkit/build-ng-packagr 0.6.5
@angular-devkit/build-optimizer 0.6.5
@angular-devkit/core 0.6.5
@angular-devkit/schematics 0.6.5
@angular/cli 6.0.5
@angular/material 6.1.0
@ngtools/json-schema 1.1.0
@ngtools/webpack 6.0.5
@schematics/angular 0.6.5
@schematics/update 0.6.5
ng-packagr 3.0.0-rc.5
rxjs 6.2.0
typescript 2.7.2
webpack 4.8.3
ng new angular-project
sh
ng g library mylibrary
ng g application myapp
ng add @angular/material myapp
Installing packages for tooling via npm.
Multiple projects are defined; please specify a project name
@angular/material
gets correclty installed in the node dependencies but the myapp
project is not configured for using the library.
The current ng add
usage is: usage: ng add <collection>
Ideally this should allow passing the target app like this:
usage: ng add <collection> [options]
options:
--project
The name of the project.
I was trying to do the same. If you do ng add @angular/material --project=my-app
it "works". What I observed was:
ng generate @angular/material:material-nav --name=app-nav
scaffolds the component on the src\app
instead of generating on the default project. You also need to append --project=my-app
to set to its correct location.ng serve --project=demo
will serve the correct appisHandset$ | async
needs to be wrapped in ()
Most helpful comment
I was trying to do the same. If you do
ng add @angular/material --project=my-app
it "works". What I observed was:ng generate @angular/material:material-nav --name=app-nav
scaffolds the component on thesrc\app
instead of generating on the default project. You also need to append--project=my-app
to set to its correct location.ng serve --project=demo
will serve the correct appisHandset$ | async
needs to be wrapped in ()