Skip to content

Conversation

@sarimarton
Copy link
Contributor

This is a PR to mitigate the issue described in #2

@sarimarton
Copy link
Contributor Author

sarimarton commented Jul 13, 2019

I wanted to open another PR for allowing minor release differences in React as a peer dependency, otherwise I can't use React hooks with cyclejs/react (without react duplication in the bundle), but then I realized that git updates this existing PR, so it became a mixed bag.

Update: I realized that NPM just warns about peer dependencies, so I can probably use any react version. I just need the peer dependency commit to be merged. Maybe I can revert the wildcard commit if it raises concerns.

@staltz
Copy link
Member

staltz commented Jul 13, 2019

@sarimarton Thanks, I now agree with you about peerDependencies

@sarimarton
Copy link
Contributor Author

@staltz Many thanks, we're almost there. Turns out, cyclejs/react-dom also needs an update, I've created a PR there.

staltz pushed a commit to cyclejs/react-dom that referenced this pull request Jul 14, 2019
After merging cyclejs/react#5, npm started to create `node_modules/@cycle/react-dom/node_modules/@cycle`, because cyclejs/react-dom currently depends on cyclejs/react-dom v2.1.0, which in turns depends on React 16.5.2... This PR is for fixing the same issue - avoid nested npm installs of peer dependencies.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants