-
Notifications
You must be signed in to change notification settings - Fork 12.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for configuration inheritance via packages #27348
Add support for configuration inheritance via packages #27348
Conversation
src/compiler/commandLineParser.ts
Outdated
return extendedConfigPath; | ||
} | ||
// If the path isn't a rooted or relative path, resolve like a module | ||
const resolved = nodeModuleNameResolver(extendedConfig, combinePaths(basePath, "tsconfig.json"), { moduleResolution: ModuleResolutionKind.NodeJs }, host, /*cache*/ undefined, /*lookupConfig*/ true); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no way to traceResolution
this. Ideally we would want to flow that option here (esp when invoked from command prompt)? To ensure users are able to find out whats going on when resolving tsconfig.json?
Ping @sheetalkamat I wired through tracing; anything else? |
I'm thrilled. Where can I see the documentation for this, please? |
Awesome! Hope to see this in the next release!!! :D |
See for more information microsoft/TypeScript#27348
Fixes #18865