Component not generated in specified directory.
See original GitHub issuePlease provide us with the following information:
- OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows 10
- Versions. Please run
ng --version
. If there’s nothing outputted, please run in a Terminal:node --version
and paste the result here:
angular-cli: 1.0.0-beta.11-webpack.2 node: 5.10.1 os: win32 x64
- Repro steps. Was this an app that wasn’t created using the CLI? What change did you do on your code? etc.
change to a directory, for example, /app/components, then run ng g component new-component
- The log given by the failure. Normally this include a stack trace and some more information.
installing component create src\app\new-component\new-component.component.css create src\app\new-component\new-component.component.html create src\app\new-component\new-component.component.spec.ts create src\app\new-component\new-component.component.ts create src\app\new-component\index.ts create src\app\new-component\shared\index.ts
- Mention any other details that might be useful.
The documentation states:
“# if in the directory src/app/feature/ and you run” ng g component new-cmp “# your component will be generated in src/app/feature/new-cmp”
so the results should have been this:
installing component create src\app\components\new-component\new-component.component.css create src\app\components\new-component\new-component.component.html create src\app\components\new-component\new-component.component.spec.ts create src\app\components\new-component\new-component.component.ts create src\app\components\new-component\index.ts create src\app\components\new-component\shared\index.ts
Thanks! We’ll be in touch soon.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (3 by maintainers)
OK, #1633 is closed, and as of Beta 15, this is still an issue, even with a brand new project.
My angular-cli.json:
I have discovered a workaround. The following commands do allow the creation of new entities in the directory of choice. Perhaps just the documentation is incorrect at this point.
$ ng g component components//my-new-component-9
installing component create src\app\components\my-new-component-9\my-new-component-9.component.css create src\app\components\my-new-component-9\my-new-component-9.component.html create src\app\components\my-new-component-9\my-new-component-9.component.spec.ts create src\app\components\my-new-component-9\my-new-component-9.component.ts$ ng g service services//my-new-service-3
installing service create src\app\services\my-new-service-3.service.spec.ts create src\app\services\my-new-service-3.service.ts WARNING Service is generated but not provided, it must be provided to be usedThe only slight problem being in app.module.ts the path ends up as (note the backslash after ‘components’):
import { MyNewComponent9Component } from './components\my-new-component-9/my-new-component-9.component';
and it has to be changed to:
import { MyNewComponent9Component } from './components/my-new-component-9/my-new-component-9.component';
I am working through some tutorials and have discovered this as well when using GitBash. From a sub-folder of the “app” folder, I tried to create a component but it simply ended up in the “app” folder. The fact that I created the component from the sub-folder was ignored.