René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"ng add fails to find app.module.ts when using custom tsconfig.json paths","articleBody":"### Bug Report or Feature Request (mark with an `x`)\r\n```\r\n- [X ] bug report -\u003e please search issues before submitting\r\n- [X ] feature request\r\n```\r\nWhether this is a bug or a feature depends on whether or not custom `paths` in `tsconfig.json` are supported with the Cli.\r\n\r\n### Command (mark with an `x`)\r\n```\r\n- [X ] add\r\n```\r\n\r\n### Versions\r\nAngular CLI: 7.0.2                                          \r\nNode: 10.8.0                                                \r\nOS: win32 x64                                               \r\nAngular: 7.0.0                                              \r\n... animations, common, compiler, compiler-cli, core, forms \r\n... http, language-service, platform-browser                \r\n... platform-browser-dynamic, router                        \r\n\r\n### Repro steps\r\n- `ng new app-name` (pick defaults)\r\n- Add `\"paths\": { \"@app/*\": [\"src/app/*\"] }` to `tsconfig.json`\r\n- Update `main.ts` to use this new path\r\n    `import { AppModule } from '@app/app.module';`\r\n    `import { environment } from './environments/environment';`\r\n- `ng add @angular/material`\r\n- Select `Yes` for `? Set up browser animations for Angular Material?`\r\n\r\nRepository all set up to reproduce this error is available [here](https://github.com/seangwright/ng-cli-add-error-with-tsconfig-paths).\r\nJust clone and type `ng add @angular/material`.\r\n\r\n### The log given by the failure\r\n`Could not read Angular module file: /src/@app/app.module.ts`\r\n\r\n### Desired functionality\r\nCli handles custom paths in `tsconfig.json`.\r\n\r\n### Mention any other details that might be useful\r\nHere is where material tries to get the `app.module.ts` path\r\nhttps://github.com/angular/material2/blob/985774a4eaa14d1dcbf1ad96ab176043d38f433e/src/lib/schematics/ng-add/setup-project.ts#L56\r\n\r\nHere is where the path to `app.module.ts` is being calculated in the schematics code\r\nhttps://github.com/angular/angular-cli/blob/82f2bda2f59e4665611d1a75b51a62bae21ac340/packages/schematics/angular/utility/ng-ast-utils.ts#L78\r\n\r\nI believe the above link is what is causing the problem.\r\n\r\nI've always preferred absolute urls in Angular apps compared to the relative paths (which become very difficult to read for nested components).\r\n\r\nAdding custom `paths` to `tsconfig.json` works pretty well to solve this problem. VSCode works fine with it and the Cli has no other issues I've run into.\r\n\r\nIf using `paths` isn't officially supported does the Angular team recommend using relative paths like `import { MyApiService } from '../../../../../my-api.service'`?\r\n","author":{"url":"https://github.com/seangwright","@type":"Person","name":"seangwright"},"datePublished":"2018-10-24T20:21:41.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":11},"url":"https://github.com/12740/angular-cli/issues/12740"}