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.

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

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.

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

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:

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

   ng g component mycomponent --skip-import

2. 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

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

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.

1. 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.

2. 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/**"
   ]
   }
   }
   }
   }
   

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

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

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.

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 { }

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

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

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

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

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!

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.

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

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.

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 ..).