Testcafe should default to using the package.json/global tsc if it exists #8031
Labels
STATE: Stale
An outdated issue that will be automatically closed by the Stale bot.
TYPE: enhancement
The accepted proposal for future implementation.
Comments
DanKaplanSES
added
the
TYPE: enhancement
need-response-app
bot
added
the
STATE: Need response
aleks-pro
removed
the
STATE: Need response
|
This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open. |
github-actions
bot
added
the
STATE: Stale
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is your Scenario?
I've been asked to break up the trade-offs listed in #7978 (comment) into separate issues so they can be discussed individually.
What are you suggesting?
This means the ts compiler you use for your production code might be different from the one in your testcafe tests. This has the potential to cause strange bugs that are difficult to track down;
tscmay compile your project fine, but TestCafe reports issues, or vice versa. It limits certain ts features to specific parts of your code base.What alternatives have you considered?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: