Ability to extend compilerOptions's paths config

# Suggestion I have a `tsconfig.base.json` file for the monorepo, it defined paths that all project can use ``` { "compileOnSave": false, "compilerOptions": { ``` "paths": { "@aegis/ui": ["libs/ui/src/index.ts"], "@aegis/ui/*": ["libs/ui/src/*"], "@aegis/shared": ["libs/shared/src/index.ts"], "@aegis/shared/*": ["libs/shared/src/*"] } }, "exclude": ["node_modules", "tmp"] } ``` Each project has own `tsconfig.json`, also defined paths that only for itself ``` { "extends": "../../tsconfig.base.json", "compilerOptions": { "paths": { "@environment": ["src/environments/environment.ts"] } }, "files": [], "include": [], "references": [ { "path": "./tsconfig.app.json" }, { "path": "./tsconfig.spec.json" }, { "path": "./tsconfig.editor.json" } ] } ``` Unfortunately, the `paths` would be overwritten. I have to add `tsconfig.base.json` paths item to each project. So, it's necessary to provide a solution for this case. ## 🔍 Search Terms <!-- 💡 Did you know? TypeScript has over 2,000 open suggestions! 🔎 Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress. The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests Replace the text below: --> - compilerOptions paths extends label:Suggestion List of

Posted by xiejay97 on Jun 15, 2021, 6:33 AM

Tags

• ux (SaaS)

Related issues

• Some good points here, and I definitely hate the "unalive" movement but like someone else said, it has gone beyond self-censorship to in-...
• It’s hard to take the article seriously when there’s no real discussion about how consciousness is defined and it takes Anthropic’s views...
• you know what i hate?
• > I honestly do not understand why any average person would buy anything else than a macbook today.
• Codex App frequently freezes/stutters on Windows 11 Pro despite sufficient system resources
• Add "Basic" and "Standard" plans