You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 26, 2019. It is now read-only.
Thanks for creating and maintaining the typescript version of create-react-app! I'm new to all of this and it's been a great help.
My question - during build, I get warnings like the following:
Warning: The 'await-promise' rule requires type checking
Warning: The 'no-use-before-declare' rule requires type checking
Warning: The 'return-undefined' rule requires type checking
Warning: The 'no-floating-promises' rule requires type checking
Warning: The 'no-unnecessary-qualifier' rule requires type checking
Warning: The 'strict-type-predicates' rule requires type checking
Is there any way to get rid of these warnings (without ejecting)? My understanding is that one has to run tslint with the --type-check option, but I'm not sure if create-react-app(-typescript) provides any hooks for that.
Thanks for any help!
The text was updated successfully, but these errors were encountered:
Thanks @jquintozamora. This will work but I was hoping to get the checks to actually run rather than disabling them. But I understand that one gives up configurability by using create-react-app, so if that's not possible so be it. Just wanted to see if that's indeed the case.
Uh oh!
There was an error while loading. Please reload this page.
Thanks for creating and maintaining the typescript version of create-react-app! I'm new to all of this and it's been a great help.
My question - during build, I get warnings like the following:
(I'm using the tslint "standard" configuration.)
Is there any way to get rid of these warnings (without ejecting)? My understanding is that one has to run
tslint
with the--type-check
option, but I'm not sure if create-react-app(-typescript) provides any hooks for that.Thanks for any help!
The text was updated successfully, but these errors were encountered: