Skip to content

[Request] Extend tsconfig via a package #15984

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

Closed
Timer opened this issue May 22, 2017 · 5 comments
Closed

[Request] Extend tsconfig via a package #15984

Timer opened this issue May 22, 2017 · 5 comments
Labels
Duplicate An existing issue was already created

Comments

@Timer
Copy link

Timer commented May 22, 2017

TypeScript Version: 2.3.2

Code

{
  "extends": "tsconfig-react-app"
}

Expected behavior:

Using the node module resolution, finds the specified package and inspects the package.json's main field for a .json file, which is used to extend the configuration.

Actual behavior:
Something along the lines "must be a relative path".

@mhegazy mhegazy added the Suggestion An idea for TypeScript label May 22, 2017
@vtabary
Copy link

vtabary commented Jun 1, 2017

I think it could use the same behavior than the module resolution to be consistent.

@Timer
Copy link
Author

Timer commented Jul 13, 2017

Would love to know if this would be considered or if I could contribute support.

We'd really like it for create-react-app. We're currently exploring TypeScript support and something that's important to us is zero-configuration, so this feature is pretty important.
Thanks!

@loucyx
Copy link

loucyx commented Nov 2, 2017

This is very simmilar to this issue: #18865 I really want to see this solved. Is currently making my dev experience really annoying.

@mhegazy
Copy link
Contributor

mhegazy commented Nov 2, 2017

Closing in favor of #18865.

Though #18865 is a duplicate of this one, #18865 seems to have more discussion.

@mhegazy mhegazy added Duplicate An existing issue was already created and removed Suggestion An idea for TypeScript labels Nov 2, 2017
@Timer
Copy link
Author

Timer commented Nov 2, 2017

I think you forgot to close :)

@Timer Timer closed this as completed Nov 2, 2017
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Duplicate An existing issue was already created
Projects
None yet
Development

No branches or pull requests

4 participants