Agfdhyk

ng g component nameComponent --module=app.module.ts

Not sure if maybe Alexander Ciesielski's answer was correct at the time of writing, but I can verify that this no longer works. It doesn't matter which directory in the project you run the Angular CLI. If you type

ng g component newComponent

it will generate a component and import it into the app.module.ts file

The only way you can use CLI to automatically import it into another module is by specifying

ng g component moduleName/newComponent

where moduleName is a module you've already defined in your project. If the moduleName doesn't exist, it'll put the component in moduleName/newComponent directory but still import it into app.module

I didn't find an answer that showed how to use the cli to generate a component inside a top level module folder, and also have the component automatically added the the module's declaration collection.

To create the module run this:

ng g module foo

To create the component inside the foo module folder and have it added to the foo.module.ts's declaration collection run this:

ng g component foo/fooList --module=foo.module.ts

And the cli will scaffold out the module and component like this:

--EDIT the new version of the angular cli behaves differently. 1.5.5 doesn't want a module file name so the command with v1.5.5 should be

ng g component foo/fooList --module=foo

You can try below command, which describes the,

ng -> Angular 

g  -> Generate

c  -> Component

-m -> Module 

Then your command will be like:

ng g c user/userComponent -m user.module

this is what worked for me :

1 -->  ng g module new-module



2 -->  ng g c new-module/component-test --module=new-module/new-module.module.ts

If you want to generate a component without its directory use --flat flag.

For Angular v4 and Above, simply use:

ng g c componentName -m ModuleName

Use this simple command:

ng g c users/userlist

users: Your module name.

userlist: Your component name.

According to Angular docs the way to create a component for specific module is,

ng g component <directory name>/<component name>

"directory name" = where the CLI generated the feature module

Example :-

ng generate component customer-dashboard/CustomerDashboard

This generates a folder for the new component within the customer-dashboard folder and updates the feature module with the CustomerDashboardComponent

Add a component to the Angular 4 app using Angular CLI

To add a new Angular 4 component to the app, use command ng g component componentName. After execution of this command, Angular CLI adds a folder component-name under srcapp. Also, the references of the same is added to srcappapp.module.ts file automatically.

A component shall have a @Component decorator function followed by a class which needs to be exported. The @Component decorator function accepts meta data.

Add a component to specific folder of the Angular 4 app using Angular CLI

To add a new component to a specific folder use the command ng g component folderName/componentName

I am having the similar issues with multiple modules in application. A component can be created to any module so before creating a component we have to specify the name of the particular module.

'ng generate component newCompName --module= specify name of module'

If you have multiple apps declared in .angular-cli.json ( e.g. in case working on feature module)

"apps": [{

    "name": "app-name",

    "root": "lib",

    "appRoot": ""

}, {...} ]

You can :

ng g c my-comp -a app-name

-a stands for --app (name)

First run ng g module newModule
. Then run ng g component newModule/newModule --flat

I am currently working on angular 5 projects and I use this particular command for generating components inside a module.

ng g c <module-name>/<new-component-name>

This command will generate component local to the module if you use normal command eg

ng g c <component-name>

it will generate component inside the app module a.k.a root module.

Note: code enclosed in <> represent user specific names.