Skip to content

Conversation

@sarimarton
Copy link
Contributor

@sarimarton sarimarton commented Jul 13, 2019

After merging cyclejs/react#5, npm started to create node_modules/@cycle/react-dom/node_modules/@cycle with the old stuff (react-dom/node_modules/@cycle/react/node_modules...), because cyclejs/react-dom currently depends on cyclejs/react-dom v2.1.0, which in turn depends on React 16.5.2... This PR is for fixing the same issue - avoid nested npm installs of peer dependencies.

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.
@sarimarton
Copy link
Contributor Author

Instead of updating the peer version of "@cycle/react": "2.1.x" to "@cycle/react": "2.2.x", I just dared to use 2.x.x instead, because it felt like it makes sense after having it as a peer, but I can change it back to the patch wildcard (2.2.x) if you like that way.

@staltz staltz merged commit 3fa826e into cyclejs:master Jul 14, 2019
@staltz
Copy link
Member

staltz commented Jul 14, 2019

Thanks!

@sarimarton
Copy link
Contributor Author

Thanks, it works perfectly now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants