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

Feature Suggestion: Allow using multiple tsconfig.jsons #11827

Closed
waderyan opened this issue Oct 24, 2016 · 4 comments
Closed

Feature Suggestion: Allow using multiple tsconfig.jsons #11827

waderyan opened this issue Oct 24, 2016 · 4 comments
Labels
Suggestion An idea for TypeScript VS Code Tracked There is a VS Code equivalent to this issue

Comments

@waderyan
Copy link

From @TylorS on October 24, 2016 1:11

Hello, I have a possible feature suggestion.

In the project I am working on at work we currently have our main tsconfig.json which points the the entry point of our application app.ts and our main external typings folder (for custom typings not yet placed on DefinitelyTyped).

However we also use a tsconfig-tests.json which we use to run all of our tests which live beside our source files with the ending in .test.ts. In each file we have to use a reference to our custom typings eg. ../../../typings/index.d.ts. It'd be wonderful to somehow allow configuring multiple tsconfigs based on file endings.

Thanks for your time!

Copied from original issue: microsoft/vscode#14242

@waderyan waderyan self-assigned this Oct 24, 2016
@waderyan
Copy link
Author

From @roblourens on October 24, 2016 1:26

A workaround is keeping your source files and test files in different folders, each with their own tsconfig files.

@waderyan
Copy link
Author

From @TylorS on October 24, 2016 2:38

Thanks for the workaround @roblourens. We'll continue to do as we have for now. Our application will be extremely large, many many files and folders, and refactoring will be quite expensive when your test folder will typically become a mirror of the source file folder.

Thank you for any work that is done here :D

@waderyan
Copy link
Author

@TylorS thank you for opening up this issue. We want to address some of these issues around configuration. This is a JavaScript language service issue. I am moving to that repo to discuss more.

@waderyan waderyan added VS Code Tracked There is a VS Code equivalent to this issue and removed typescript labels Oct 24, 2016
@waderyan waderyan removed their assignment Oct 24, 2016
@RyanCavanaugh
Copy link
Member

#9876 should handle nearly all use cases here. If there's something that doesn't work for, please log a separate issue outlining exactly how you'd like something to work. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Suggestion An idea for TypeScript VS Code Tracked There is a VS Code equivalent to this issue
Projects
None yet
Development

No branches or pull requests

2 participants