Skip to content

Support more tsconfig.json scenarios #301

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
brphelps opened this issue Oct 5, 2016 · 2 comments
Closed

Support more tsconfig.json scenarios #301

brphelps opened this issue Oct 5, 2016 · 2 comments
Labels
help wanted Contributions are especially encouraged

Comments

@brphelps
Copy link

brphelps commented Oct 5, 2016

Right now, the tsconfig.json reader is somewhat limited -- it's only looking for "files" sections and doesn't take into account other significant parameters like "exclude" and "compilerOptions.rootDir".

Since these are critical to being able to process a tsconfig.json the same way a TypeScript compiler would, support should be added.

@blakeembrey blakeembrey added enhancement help wanted Contributions are especially encouraged labels Oct 11, 2016
@aciccarello
Copy link
Collaborator

aciccarello commented Dec 2, 2016

I took a look at the status of Typescript 2.0 support. As a workaround, several options were temporarily ignored via #308 to allow builds to continue but people using the new features may not be able to compile. See #234 for the original discussion.

feature issues PRs status
baseUrl #340 #342 Merged
paths #340 #342 Merged
include #326 #359 Merged
lib #315 Ignored
types #311 Ignored
typeRoots #305 Closed
rootDirs #386 Open
extends #380 Open

@Gerrit0
Copy link
Collaborator

Gerrit0 commented Dec 27, 2020

As far as I know - 0.20 respects all compiler options and behaves the same as tsc does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Contributions are especially encouraged
Projects
None yet
Development

No branches or pull requests

4 participants