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

How to specify path to tsconfig.json #457

Open
joonhocho opened this issue Jul 13, 2019 · 6 comments · May be fixed by #914
Open

How to specify path to tsconfig.json #457

joonhocho opened this issue Jul 13, 2019 · 6 comments · May be fixed by #914
Labels
enhancement New feature or request

Comments

@joonhocho
Copy link

I have multiple tsconfig.json files one for build (tsconfig.build.json) and one for coding (tsconfig.json).
For coding, I add test files as well since I want to type check test files.
For building, I only add source files.
ncc is by default using tsconfig.json so it also include test files.
Any way to specify custom tsconfig.json path?

@tomsseisums
Copy link

Stumbled on this necessity too... skimmed through the source, there's isn't a way to do it yet.

@viceice
Copy link

viceice commented Mar 23, 2020

Would you accept a pr for this?

@PaulRBerg
Copy link

This would be great to have!

@styfle styfle added the enhancement New feature or request label Jun 22, 2021
@styfle
Copy link
Member

styfle commented Jun 22, 2021

Would you accept a pr for this?

Yep! If you want to submit a PR and a test, we'll take a look 👍

@mreis1
Copy link
Contributor

mreis1 commented Jan 16, 2023

Hello guys, is this PR being integrated any time soon?

@vtgn
Copy link

vtgn commented Jun 14, 2023

Hello, what's new about this?
This is very embarrassing to not be able to set the tsconfig file to use. :/
For example, the NestJs framework standard is to name the tsconfig file tsconfig.build.json for the code only, extending the tsconfig.json file used for code and test.
Without this feature, we cannot respect the NestJs standard. :(
Regards.

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

Successfully merging a pull request may close this issue.

7 participants