Skip to content
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

Testcafe's tsconfig settings are different from standard tsconfig defaults and some are undocumented. #8032

Open
DanKaplanSES opened this issue Oct 10, 2023 · 1 comment
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
Copy link

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?

TestCafe passes the following options to the TypeScript compiler unless you override them:

Option Value
allowJs true
emitDecoratorMetadata true
experimentalDecorators true
inlineSourceMap true
noImplicitAny false
pretty true
suppressOutputPathCheck true
skipLibCheck true

These aren't always aligned with tsconfig defaults. This can make your tsconfig appear strange relative to the typical tsconfig: if you want to remove one of these settings, you add the property.

You can override some but not others. e.g., you can't modify target (at least, I think that's why I errors/warnings about it sometimes). If I'm correct about testcafe being the source of those, I don't think this table is comprehensive: target isn't mentioned.

I don't even know what suppressOutputPathCheck is, as it's not officially documented.

What alternatives have you considered?

No response

Additional context

No response

@DanKaplanSES DanKaplanSES added the TYPE: enhancement The accepted proposal for future implementation. label Oct 10, 2023
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Oct 10, 2023
@aleks-pro aleks-pro removed the STATE: Need response An issue that requires a response or attention from the team. label Nov 10, 2023
Copy link

github-actions bot commented May 9, 2024

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 github-actions bot added the STATE: Stale An outdated issue that will be automatically closed by the Stale bot. label May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATE: Stale An outdated issue that will be automatically closed by the Stale bot. TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Development

No branches or pull requests

2 participants