Closed andykais closed 4 years ago
Yeah, the problem is here https://github.com/parcel-bundler/parcel/blob/master/packages/core/parcel-bundler/src/assets/TypeScriptAsset.js#L37
parcel just uses tsconfig.compilerOptions
without try to parse this config by typescript internal tools which should normalize config by reading extends and etc
ah, good to know. Is there an issue already open in parcel-bundler?
So, I don't see anything
actually it looks like a bug has already been reported https://github.com/parcel-bundler/parcel/issues/2856
Fixed in parcel@2
I have tsconfig files in a folder
tsconfig/
. I added a topleveltsconfig.json
file with the contentsso my project directory looks like so:
I created this file specifically so this plugin can find my nested configs. Unfortunately it does not seem to notice the tsconfigs in the
tsconfig/
folder. I know it does not because I have tried leaving an invalid json file in tsconfig/tsconfig.json and parcel still builds without issue. On a related note, if I could specify the location of my tsconfig file like I can withttsc
, I could avoid these extra steps.