-
Notifications
You must be signed in to change notification settings - Fork 4
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
Install react packages as dev dependencies #67
Conversation
Move react, react-dom and prop-types to dev dependencies.
I think this will stop Markdownz from installing React 15 when the parent project is using React 16. |
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.
This is working with the react 16 branch.
Similar to my comment on zooniverse/Seven-TenClient#react-dependency, using peer dependency might be more appropriate.
Should zooniverse/modal-form use peer dependencies too? We've not declared them before. |
I think they might be a better way to go for long term maintenance. I had the same thought as you that they were deprecated, but I learned from the grommet team that they are not, just the auto-install part was deprecated. |
Would something like peerDependencies: {
"react": ">= 15.6"
} include all versions since 15.6, including 16? |
Hm, I'm not sure if that would include 16. The grommet source uses an |
That's going to be painful when the major version changes again. |
Let's see if the latest commit throws a warning with React 16. |
Published as 7.6.0. |
Move react, react-dom and prop-types to dev dependencies.