Skip to content
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

Merged

Conversation

weswigham
Copy link
Member

Fixes #18865

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);
Copy link
Member

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?

@weswigham weswigham added this to the TypeScript 3.2 milestone Oct 5, 2018
@weswigham
Copy link
Member Author

Ping @sheetalkamat I wired through tracing; anything else?

@weswigham weswigham merged commit 05716a7 into microsoft:master Oct 25, 2018
@weswigham weswigham deleted the config-inheritance-through-modules branch October 25, 2018 17:20
@mightyiam
Copy link

I'm thrilled. Where can I see the documentation for this, please?

@kristianmandrup
Copy link

Awesome! Hope to see this in the next release!!! :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants