Allow for dropping tsconfig.json in arbitrary folder and specifying the source root with tsc command

Search Terms

1. tsconfig.json
2. TS18003
3. project root

Suggestion

I have been deving an automation publish tool, with typescript inside. Nice work for you!

Since the tsconfig.json file need to be put in a center config folder other than project/source code root. amd i have tried to use tsc --watch --project path-to-tsconfig.json to make this future, which is not working for now.

I got TS18003 error, and i know why this happen: tsc just want to remind us we may have a wrong include or exclude config. 😄 I cannot find any tsc command should i use to conject with --project option to specify the project root.

I find in the tsc sourcecode that the compiler.parseJsonConfigFileContent(_, _, basePath); function could let us specify the project basePath when parsing tsconfig.json, so, i want to ask if we can expose a command option to let use the same function as basePath, maybe --configFileBasePath or --configContext?

Please let me know if there already is a solution for my use case.

Thank you for your works!

Examples

tsc --project path-to-tsconfig.json --configContext path-to-source-code-root

Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript / JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. new expression-level syntax)

Start with the tsc --project handling and the compiler.parseJsonConfigFileContent call mentioned in the issue. Trace how tsconfig.json paths determine the project base path and how TS18003 is produced. Done means a documented command option can specify a separate source root for a config in an arbitrary folder, with tests covering the example invocation.