-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Peer dependency chain break when using yarn PnP #2014
Comments
Anyone solve this? In my case, |
I have switched to recharts which has way better performance, ...but then I ditched PnP afterwards anyways. It's just not ready to be used in semi-big projects. |
This is a workaround via
Unfortunately the latest Nivo |
Whoo! Working for me with the 2 workarounds mentioned above (#2014 (comment)) and in #1941 (#1941 (comment)) |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment! |
bump |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you! |
I'm trying to address this issue in #2313. |
Describe/explain the bug
When using nivo with yarn PnP, it detects a peer dependency error in multiple nivo packages.
Full log output can be found here: https://drone.mauz.io/MauriceNino/dashdot/148/1/3
To Reproduce
Check out https://github.com/MauriceNino/dashdot, switch to branch
feature/yarn_pnp
and runyarn && yarn build
.Additional context
react-spring has a peer dependency to react-dom, so you should forward it, or install it.
The text was updated successfully, but these errors were encountered: