-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
allow per file compilerOptions #31035
Comments
"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 |
If you have two libraries A and B and compile them to .js and .d.ts can't you use them in file C? |
This issue has been marked as "Too Complex" and has seen no recent activity. It has been automatically closed for house-keeping purposes. |
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.
The text was updated successfully, but these errors were encountered: