GeezerVison is showing github.com — Ng generate always assumes an `app` folder · Issue #9370 · angular/angular-cli
Ng generate always assumes an app folder #9370DescriptionOur project setup doesn't have an immediate sub-folder of app, however, it appears that running ng generate always assume that you have an app folder under the app root folder you specified in .angular-cli.json
Versions
Angular CLI: 1.6.0
Node: 7.0.0
OS: darwin x64
Angular:
...
Repro steps
- Setup a simple .angular-cli.json with:
{
"apps": [
{
"name": "client",
"root": "projects/client"
}
]
}
ng g c form-inputs/mike --skip-import --dry-run --app=client
Observed behavior
You'll see the output path always assumes an app folder:
create projects/client/app/form-inputs/mike/mike.component.css (0 bytes)
create projects/client/app/form-inputs/mike/mike.component.html (23 bytes)
create projects/client/app/form-inputs/mike/mike.component.spec.ts (614 bytes)
create projects/client/app/form-inputs/mike/mike.component.ts (261 bytes)
Desired behavior
I'd like an option to be able to configure whether your project has the app folder or not. Or maybe an option to configure the whole path the component gets created in. Reacted by ekumpe, Michael McDonald, Ben Elliott, Eduard Kolosovskyi, John Crim, Ruffin, Nguyen Tran Tan An, Lars Berger, Denis Bendrikov and Martin Sikora Activitychanged the title [-]Ng generate assumes an `app` folder[/-] [+]Ng generate always assumes an `app` folder[/+] on Jan 24, 2018PoiScript commented on Feb 1, 2018 Actually, there is an undocumented option in .angular-cli.json called appRoot which is probably you're looking for. Reacted by Martin Sikora, Bruno Mayer Paixão, codeepic, Ryan Pivovar and Miquel Canal martinsik commented on Feb 13, 2018 leonadler commented on Jun 19, 2018 Using appRoot leads to an error "Workspace needs to be loaded before it is used."
and is not included in the json-schema for angular.json. PoiScript commented on Jun 19, 2018 jacobjojan commented on Jul 10, 2018 ng generate is adding app to the path by default. How to remove 'app' ?
"root": "",
"sourceRoot": "ui-lib/src",
"projectType": "library",
ng g module dashboard/widget -d
CREATE src/app/dashboard/widget/widget.module.spec.ts (275 bytes)
CREATE src/app/dashboard/widget/widget.module.ts (190 bytes) Reacted by Leon Adler, Wasif Ali, Bruno Mayer Paixão, Colby Rome, Michael McDonald, Umut Akkaya, Ruffin, Gary Alfred, Ryan Knittel and Nathaniel A Collier wasif-digitalnet commented on Aug 1, 2018 I'm having the same issue as @jacobjojan, every time I run ng generate it generates by default in app folder, I want to generate out of app folder, how to do that? giolf commented on Aug 22, 2018 @wasif-digitalnet what about
ng generate module ../my-module
CREATE src/my-module/my-module.module.spec.ts (292 bytes)
CREATE src/my-module/my-module.module.ts (192 bytes)
Reacted by Wasif Ali, Elio Maggini, Deepak Pathak, Colby Rome, Michael McDonald, apijay20, Thomas Cayne, Chetan Baadkar, Elio Maggini, sajidnovateus and 7 more Reacted by Ruffin wasif-digitalnet commented on Aug 28, 2018 @giolf I have tried it, I guess there was some issues while generating the project, I made a new project and it's working fine now, giolf commented on Aug 28, 2018 @wasif-digitalnet probably you run that command in a nested folder of your project ?
Anyway I’m glad to hear that you could solve it ilivestrong commented on Oct 8, 2018 @giolf Your solution worked... Cheers! Paitum commented on Jul 31, 2019 This problem is still unresolved.
We have a code-base similar to Angular Material, where the library modules folders are directly beneath the main library folder.
We have recently replaced our custom build systems in favor of the Angular CLI, but when using the ng generate commands, they automatically add either app or lib depending on the project type (application or library).
Why can't this be configurable? Why isn't "sourceRoot" the literal root? Reacted by Umut Akkaya, John Crim, Terry Brown, Noorsil Karedia, Ruffin, Gary Alfred, Lars Berger, Nguyen Tran Tan An, mossiomylv, Nathaniel A Collier and 1 more angular-robot commented on Feb 1, 2022
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.
Find more details about Angular's feature request process in our documentation. angular-robot commented on Feb 21, 2022
Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.
We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.
You can find more details about the feature request process in our documentation. umagon commented on Aug 6, 2025 Reacted by Gavin Campbell
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|