Repository navigation
allow per file compilerOptions #31035
Description
Activity
"Too Complex" is probably an understatement here. It's not really even clear what this means - if you have a type declared in file A, another type in file B, and you try to relate them in file C, whose value of
strictFunctionTypesis in play? What happens when you try to use a type whose declaration is illegal in the current file scope? The questions never stop, and none of them have clear or predictable answers.Reacted by David Sherret, Zzzen and Shivam DwivediIf you have two libraries A and B and compile them to .js and .d.ts can't you use them in file C?
So what is the difference to your case ? The problem already is there.Reacted by Avi Mehra and Paul DraperThis issue has been marked as "Too Complex" and has seen no recent activity. It has been automatically closed for house-keeping purposes.
Reacted by Denis Bendrikov, Niklaas Baudet von Gersdorff, Abdullah Hilson and Shoghy Martinez
Search Terms
Allow to set compilerOption for each file
Suggestion
Having multiple "references" dependencies sucks because there is still much redundancy in managing dependencies such as having to add "refrerences" and still add it to your node_modules by a tool like fyn - also for small library (maybe single files) it seems to be some overhead.
It looks smarter to just have one ts process manage everything (mono repo) like, eg see https://github.com/MarcWeber/tsmono which allows linking dependencies so that you can use them as they were part of the current repository thus no wasting time writing intermediary .js files or the like which eventually needs to be transpiled again.
There is one big problem: The dependencies might have different compiler options.
So it would be nice if compiler options could be specified on a per file basis.
The most stupid implementation could be s.th like
tsconfig.json be optionally a list containing many tsconfig configurations.
Then include/exclude could be used.
Example: tsconfig.json's contents
Maybe there are more solutions to this. Thus opening this issue to see how many more uses case might exist.