angular-cli: Cannot create components with CLI on Windows

I had the same problem after upgrading a project from Angular 4.3 to Angular 6. The problem turned out to be the sourceRoot value in angular.json under the [project-name]-e2e project. It was set to “e2e”. When comparing to other projects created initially with Angular 6 (not upgraded), I noticed that they had an empty string specified for sourceRoot on the e2e project. After changing mine to that configuration, this problem was resolved.

Please note that sourceRoot for the primary project should still be “src”, you should only need to change it to an empty string on the e2e project.

I’m having the same problem. “Upgraded” to Angular 6, and now I can no longer generate components, services, etc.

“Could not find an NgModule”

A temporary workaround is switching to bash on windows when using ng generate.

This should really be a highly prioritized bug to fix.

Angular CLI: 6.0.7 Node: 8.9.0 Angular: 6.0.3

use --skip-import flag to ignore this message because otherwise angular-cli will look for a module to declare the component and if it can’t find it it won’t generate component. try this and it should work.

ng g component components/news/news --skip-import

I am creating a project to support multiple apps and ran into a similar (or perhaps same) scenario. For starters, I’m using @angular/cli@1.5.0-beta.4 (on Windows) since I needed appRoot support. The basic directory structure is similar to .NET Core features where all code is grouped by folders and client code lives right next to server code, which is why appRoot is called Client. I’ve pushed the common Angular config files to the root so they are shared across apps, so the structure is as follows (I’ve obviously left out some files from this listing):

TestProject\Group1\Feature1\Client (contains main.ts, app.module.ts, and app.component.ts)
TestProject\Group1\Feature2\Client (contains main.ts, app.module.ts, and app.component.ts)
TestProject\angular-cli.json

More importantly, here are the associated CLI config values:

"apps": [
    {
      "name": "feature1",
      "root": "Group1/Feature1",
      "appRoot": "Client",
      "prefix": "feature1",
      ...
    },
    {
      "name": "feature2",      
      "root": "Group1/Feature2",
      "appRoot": "Client",      
      "prefix": "feature2",
      ...
    }
   ],

When I run the command with --skip-import and dry run, I get the following as others have been observing:

ng g c foo --skip-import -d
create Group1/Feature1/Group1/Feature1/Client/foo/foo.component.html (22 bytes)
create Group1/Feature1/Group1/Feature1/Client/foo/foo.component.ts (238 bytes)

Without skip-import, it’s also unable to track down the module to add it to as a result of the wrong path.

I spent some time adding logging to the angular-cli code and came up with the following findings that I hope will help troubleshoot this: In generate.ts, the run function had the following values: parsedPath value

{
	root: '\\',
	dir: 'Group1\\Feature1\\Client',
	base: 'foo',
	ext: '',
	name: 'foo',
	appRoot: 'Group1\\Feature1\\Client',
	sourceDir: 'Group1/Feature1'
 }

commandOptions values

• path: Group1/Feature1/Client
• appRoot: Group1\Feature1\Client
• sourceDir: Group1/Feature1

When seeing the behavior in find-module.js, it looks like the root problem there is in the way that it builds out the pathToCheck. findModuleFromOptions

• options.sourceDir: Group1/Feature1
• options.path: Group1/Feature1/Client

pathToCheck logic

        const pathToCheck = (options.sourceDir || '') + '/' + (options.path || '')
            + (options.flat ? '' : '/' + strings_1.dasherize(options.name));

resulting pathToCheck value Group1/Feature1/Group1/Feature1/Client/foo

I took a quick look in the component\index.js file that is used to create components and it has similar logic:

        const componentPath = `/${options.sourceDir}/${options.path}/`
            + (options.flat ? '' : stringUtils.dasherize(options.name) + '/')
            + stringUtils.dasherize(options.name)
            + '.component';

I’m not sure what the exact fix is since this code has to support multiple combinations of command option values, but hopefully this helps isolate the issue. Thanks.

So Angular doesn’t currently work on Windows? I’m working through the tutorial and I got stuck here:

ng generate component heroes
Could not find an NgModule. Use the skip-import option to skip importing in NgModule.

I agree with @vilic This should really be fixed ASAP. If some contributor would tell us what info does he need to fix this, I’ll be more than pleased to help him.

I have the same problem after upgrading to Angular 6, same versions as the user above me.

@jeffreymichell facing same issue after upgrading to angular 6. Has anyone able to fix the issue ?

Still having this problem. Cannot generate any components on Windows. Incredibly annoying to deal with.

For now, the best solution for me is explicitly adding import module path: ng g c moduleName --module='app.module.shared.ts'