-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
CLI (React Native): ensure having an explicit dependency on prop-types
#1714
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Hypnosphi great catch. i thought about this but got lazy .. thanks for picking up the slack!
Looks like prop-types
wants to be in dependencies
though, not devDependencies
:
Codecov Report
@@ Coverage Diff @@
## master #1714 +/- ##
=======================================
Coverage 21.23% 21.23%
=======================================
Files 252 252
Lines 5702 5702
Branches 683 685 +2
=======================================
Hits 1211 1211
+ Misses 3970 3956 -14
- Partials 521 535 +14
Continue to review full report at Codecov.
|
@shilman Not in that particular case, as stories are part of development process, and the app/lib itself may not use |
Do we need to do this for the other project types also? (i.e. React/Meteor) |
No, as we don't have usages of |
Gotcha, good call! 👍 |
This is a follow-up to #1710
It's safer to have a direct dependency to anything you import from your code