Could not find an NgModule. Use the skip-import option to skip importing in NgModule

Question

I get the error in the subject of this post when I use the CLI to create a new component: ng g c my-component --project=my-project (No component is created)

I've seen other posts with the same error message, but none of them also include Nrwl/Nx, which I believe is somehow involved. Project started as Ng4 and was upgraded to Ng6.

Environment:

Angular CLI: 6.0.8
Node: 8.9.4
OS: win32 x64
Angular: 6.0.6
@angular-devkit/architect 0.6.8
@angular-devkit/build-angular 0.6.8
@angular-devkit/build-optimizer 0.6.8
@angular-devkit/core 0.6.8
@angular-devkit/schematics 0.6.8
@angular/cdk 6.3.1
@angular/cli 6.0.8
@angular/material 6.3.1
@ngtools/webpack 6.0.8
@schematics/angular 0.6.1
@schematics/update 0.6.8
rxjs 6.2.1
typescript 2.7.2
webpack 4.8.3
nrwl/nx 6.1.0

UPDATE #1

I tried dropping the --project flag entirely ( so just ng g c my-component) and still get the same problem. Not sure what that means, yet.

Please try this approach [stackoverflow.com/a/53696599/2668045](https://stackoverflow.com/a/53696599/2668045) Should be ok. — Arif Dewi, Dec 09 '18 at 20:59

score 162 · Answer 1 · answered Jul 12 '18 at 04:47

162

Quick fix

1) Change current directory in cmd/terminal to src/app

cd src/app (linux)

cd .\src\app\ (windows)

2) Run commands now

ng g c myComponent

answered Jul 12 '18 at 04:47

Debojyoti

4,503
3
19
27

4

The reason why this works, is that your project's default src/app folder hierarchy has been changed. Therefore, anything else that doesn't fit this situation will not work. When you generate a default project with cli, you shouldn't have to do this. – carkod Nov 11 '18 at 03:57
2

That is not the only reason, if you run the `ng generate component` in a folder different to `src/app` you will get that error. – Mauricio Gracia Gutierrez Mar 07 '21 at 03:05

bvdb · Answer 2 · 2019-03-18T17:31:55.157

36

The generate of components aims to do 2 things:

create source code for the component
registers the component in a module (by default, in the app.module.ts)

The problem is, that you don't have an app.module.ts. You renamed it to something else, or perhaps even have multiple of them. In that case there are 2 possible solutions:

you do the registration of the component manually. (easiest)

ng g component mycomponent --skip-import
you specify the module with the -m switch. (might be broken) There is a long thread about it here: https://github.com/nrwl/nx/issues/526

edited Mar 18 '19 at 17:31

answered Mar 18 '19 at 17:16

bvdb

22,839
10
110
123

Or you moved app.module.ts to another folder such as modules folder – Uri Gross Oct 17 '21 at 07:14
or you are not in src/app folder so app.modules.ts is not available in the current. see the reply from @Debojyoti – tuxdost Aug 25 '23 at 16:10

score 22 · Answer 3 · answered Oct 11 '19 at 18:11

22

Run component generation command(ng g c component-name) from where the app.module.ts file is located.

answered Oct 11 '19 at 18:11

Muzaffar Mahmood

1,688
2
17
20

score 16 · Answer 4 · edited Nov 19 '21 at 02:25

16

You are not inside app folder... cd app on windows, and then run command

edited Nov 19 '21 at 02:25

Nimantha

6,405
6
28
69

answered Dec 09 '20 at 11:31

Nenad Štrbić

367
4
6

Harish Cholla · Answer 5 · 2020-10-04T11:18:34.620

9

Working 100%

Try --skip-import

ng g c mycomponent --skip-import

or change directory src/app ;

open the terminal on click on app -> enter comand ng g c 'your component name' and hit enter

I think These are the error you getting click once and check it https://i.stack.imgur.com/RSG7c.png

edited Oct 04 '20 at 11:18

answered Oct 03 '20 at 15:41

Harish Cholla

199
2
4

tarÚn kÚmar · Answer 6 · 2020-06-16T10:29:05.583

8

Your current directory in cmd window matters. Run this command from the 'src/app' folder in the project. It should work.

edited Jun 16 '20 at 10:29

answered Apr 12 '20 at 13:57

tarÚn kÚmar

81
1
2

score 3 · Answer 7 · edited Jul 25 '19 at 10:42

3

I removed the line "cli": { "defaultCollection": "@nativescript/schematics" } from angular.json file and it worked for me.

edited Jul 25 '19 at 10:42

ZF007

3,708
8
29
48

answered Jul 25 '19 at 10:20

Koustav

556
5
7

score 2 · Accepted Answer · edited Nov 27 '21 at 12:42

I ended up totally deleting node_modules, clearing out the yarn cache and then running yarn to reinstall all packages. I also edited my angular.json file so that my pathing looked like this for all applications and libraries:

"root": "libs/my-lib",
"sourceRoot": "libs/my-lib/src"

I'm not sure which of those fixed the problem, but all appears to be OK now. At least the immediate problem went away.

score 2 · Answer 9 · edited Nov 11 '18 at 11:19

2

I had the same issue, In angular.json file, I searched for my-project-e2e (replace my-project with your project name) and then I changed:

"root": "" to "root": "e2e" and saved it. Everything was working again.

The solution was specified in this link.

edited Nov 11 '18 at 11:19

carkod

1,844
19
32

answered Aug 08 '18 at 16:25

lanchana gupta

330
1
3
11

score 2 · Answer 10 · edited Aug 11 '19 at 04:58

First way:
I think first you have to go to inside your app folder then type cmd;
ng g c your_com_name --spec false
or ng g c your_com_name
It will definitely create your component or solve your problem.

second way:
Remove your e2e from your angular.json->projects:
definitely

{ 
    your_project_name-e2e:{}
}

example: my-first-app-e2e

{
      "root": "e2e/",
      "projectType": "application",
      "architect": {
        "e2e": {
          "builder": "@angular-devkit/build-angular:protractor",
          "options": {
            "protractorConfig": "e2e/protractor.conf.js",
            "devServerTarget": "my-first-app:serve"
          }
        },
        "lint": {
          "builder": "@angular-devkit/build-angular:tslint",
          "options": {
            "tsConfig": "e2e/tsconfig.e2e.json",
            "exclude": [
              "**/node_modules/**"
            ]
          }
        }
      }
    }

score 2 · Answer 11 · answered May 01 '20 at 02:05

2

This is pretty weird answer, but the problem occur because I have open my project in the src directory only. Reopening the entire project folder resolves the issue.

answered May 01 '20 at 02:05

melo

56
1
3

I think this is the simplest answer to this issue. The users should be in the root folder while performing Angular CLI commands. – Joseph Jojo John May 31 '20 at 19:30

Manuel · Answer 12 · 2020-09-22T15:01:25.600

2

You may have changed the file app.module.ts to other folder (out of folder app). Ionic is not finding the file.

edited Sep 22 '20 at 15:01

answered Sep 22 '20 at 13:47

Manuel

21
3

score 2 · Answer 13 · answered May 31 '21 at 19:58

2

Make sure you are in the right path (I mean in the path you are working in) so just verify this in the console by print working directory (pwd) and change it. This worked for me

answered May 31 '21 at 19:58

Ina Tiganas

61
2

score 2 · Answer 14 · answered Sep 17 '21 at 06:31

2

Please check the location for .module.ts file. I was running this command from /src folder, while app module was inside /src/app folder.

When run the same command from /src/app path. It is working.

answered Sep 17 '21 at 06:31

Laky

29
2

score 2 · Answer 15 · answered Jan 27 '22 at 11:04

2

Enter ** cd .\app\ ** in the terminal or type "cd app + Tab". Once you are in the app folder, the ng command works!

answered Jan 27 '22 at 11:04

Miguel Angel

21
1

score 1 · Answer 16 · answered Jul 26 '19 at 11:30

1

This also happened to me and in my case it was due to me generating a new component outside of the app folder, I bought the new component inside the app folder and the issue was solved.

answered Jul 26 '19 at 11:30

score 1 · Answer 17 · answered Apr 26 '23 at 23:24

Hopefully helps someone, I had 2 issues:

I had 2 modules on the same folder level as app.module.ts that referenced NgModule, I moved it to a separate folder
My components folder was outside of the app folder, you have to be cded into app in order to run the command for it to find NgModule

score 0 · Answer 18 · answered Nov 05 '18 at 04:21

0

Had same issue. Turned out to be somehow related to the name of the root component. Renaming back to 'app' resolved the problem

answered Nov 05 '18 at 04:21

Aleksei Protopopov

1
1

score 0 · Answer 19 · answered Jul 15 '20 at 09:16

I had the same issue. My problem (in ionic 4) was that the file app-routing.module.ts was missing. I had to create an empty one, before adding new pages worked:

import { NgModule } from '@angular/core';
import { PreloadAllModules, RouterModule, Routes } from '@angular/router';

const routes: Routes = [
    {
        path: '',
        redirectTo: 'home',
        pathMatch: 'full'
    },
];

@NgModule({
    imports: [
        RouterModule.forRoot(routes, { preloadingStrategy: PreloadAllModules })
    ],
    exports: [RouterModule]
})
export class AppRoutingModule { }

score 0 · Answer 20 · answered Jul 07 '21 at 03:34

0

From visual studio code I made a: right click on the app folder -> click on "open in integrated terminal -> run the cmd: ng g component user. 4 files have been created. It works successfully!

answered Jul 07 '21 at 03:34

Esdras Clairmius

1

score 0 · Answer 21 · answered Aug 31 '22 at 08:04

0

I created empty folder my own and move my old module into it. After when I tried to create component inside the folder I got same error. I deleted the empty folder and create module folder. After that I was able to create new components etc.

answered Aug 31 '22 at 08:04

Melih

1
2

score 0 · Answer 22 · answered Nov 08 '22 at 19:35

I got this same error because I was in the wrong file location. For some reason I thought I had to do it from the file location src instead of the location above (where angular.json is and ofcourse src/ itself)

Doing the command from root location solved it (in my case cd ..).

score 0 · Answer 23 · answered Mar 27 '23 at 16:47

0

you have to move to the src/app folder

simple use $cd app command to go inside

answered Mar 27 '23 at 16:47

RONAK THAKOR

1

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Apr 02 '23 at 15:24

Could not find an NgModule. Use the skip-import option to skip importing in NgModule

23 Answers23

Quick fix

Working 100%

or change directory src/app ;

Linked

Related