Closed benrhere closed 3 years ago
@benrhere, yes, @nivo/core
is now a required dependency, and you should get warnings about it when installing, it's indicated in the generated code snippets on the website.
I also updated the README, we overlooked this one, thank you!
Thanks for using nivo
Before creating an issue...
Are you asking a question?
Please don't file GitHub issues to ask questions. Try to use the discord channel first: https://discord.gg/n7Ft74f.
Describe/explain the bug According to the readme: "In order to use nivo, you just have to pick the scoped @nivo packages according to the charts you wish to use."
This used to be true. But starting recently (not sure of the exact version), I have had to take an explicit dependency on "@nivo/core" in my package.json. If I do not, this package does not get installed and then when I run webpack I get:
Also interesting: when I point to the latest @nivo/core (0.66.0) I get several of these warnings on npm install: npm WARN @nivo/bar@0.66.0 requires a peer of @nivo/core@0.65.0 but none is installed. You must install peer dependencies yourself.
To Reproduce
npm init react-app ./my-react-app
"@nivo/bar": "0.66.0",
to the dependenciesnpm install
core
folder is absent.Expected behavior A
core
folder should be present, I believe, without an explicit dependency on this package, or the documentation should be updated.Desktop (please complete the following information):
Additional context Add any other context about the problem here.