Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support relative pathing for `ng generate` statements

Open
#6,684 2 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
angular, typescript
Domain
cli, tooling

Research direction

Reproduce the issue from the project root with ng g component ./src/app/components/test and inspect how the Angular CLI generator resolves that relative path. Done means the generated files are placed under the existing src/app directory without creating a duplicated src/app/src/app path.

Written by the indexing model from the issue text.

Description

area: @schematics/angular feature feature: insufficient votes
Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request
Versions.
node: 6.10.2
os: linux x64
@angular/common: 4.1.3
@angular/compiler: 4.1.3
@angular/core: 4.1.3
@angular/forms: 4.1.3
@angular/http: 4.1.3
@angular/platform-browser: 4.1.3
@angular/platform-browser-dynamic: 4.1.3
@angular/router: 4.1.3
@angular/cli: 1.0.4
@angular/compiler-cli: 4.1.3
Repro steps.

From project root:

ng g component ./src/app/components/test
The log given by the failure.
installing component
  create src/app/src/app/components/test/test.component.scss
  create src/app/src/app/components/test/test.component.html
  create src/app/src/app/components/test/test.component.spec.ts
  create src/app/src/app/components/test/test.component.ts
Desired functionality.

Doesn't create src/app under the (already existing) src/app directory.

This is a minor change, but would then allow me to use autocomplete with the generator, even if the immediate fix is to just remove 'src/app' from the file location input before processing.

Mention any other details that might be useful.
Dominant language
TypeScript
Stars
27k
Forks
11.8k
Avg merge
16h 35m
Merged PRs (30d)
176

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from angular/angular-cli

All issues in angular/angular-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.