add --tsconfig-path option for CLI & support extends property in tsconfig.json

[nokazn]

Overview

Hi, there!
I've made a PR to add a new CLI option and resolve potential problems. If there is something wrong or missing, feel free to point it out.
Thank you.

Changes

• add --tsconfig-path to specify path to tsconfig.json file for CLI option
  • if path to tsconfig.json is passed by this option, ncc sees that path directly, or if not, ncc resolve path to tsconfig.json as before
• support extends property in tsconfig.json
  • use officially provided API by TypeScript to resolve and parse compilerOptions & extends property
  • add param-case to convert values at jsx option to kebab-case
  • use tsconfck to parse tsconfig.json options.

Related

• resolve How to specify path to tsconfig.json #457

[styfle]

This doesn't seem very future proof.

Is there a way to have TypeScript convert this for us?

[nokazn]

@styfle
I see.
I cloudn't find a way to get complete config objects by TypeScript, but I found tsconfck from microsoft/TypeScript#44573.

Does this library look future proof, do you think? If you think it's OK, I will rewrite src/utils/load-tsconfig-options.js.

[nokazn]

I rewrited this & related parts by 5d85cd2, which uses tsconfck.
Would be glad to review it.

[TheRealBarenziah]

This is a great feature, thanks nokazn! 👏
I hope your work will be merged soon as ncc TS support is incomplete without it. Unfortunately, since ncc lacks preinstall script it's a hassle to use the fork in the meantime.

[mreis1]

Why is still on hold? Thanks for the PR

[YElyousfi]

Hello, when can we expect this to PR to be merged?

[steverhoades]

Very interested in this addition. Is there anything I can do to help get this across the finish line?

[vtgn]

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.