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
We don't intend to enable it because many people are starting to use Flow for static type analysis instead of runtime PropTypes. You can, however, eject and enable it if you'd like.
Is this a bug report?
Maybe
Can you also reproduce the problem with npm 4.x?
yes
Which terms did you search for in User Guide?
proptypes
eslint
Environment
node -v
: v6.5.0npm -v
:5.5.1yarn --version
(if you use Yarn): 0.18.1npm ls react-scripts
(if you haven’t ejected): [email protected]Then, specify:
Steps to Reproduce
npm start
Expected Behavior
I'd expect to get warnings about not having proptypes
Actual Behavior
No warnings
The text was updated successfully, but these errors were encountered: