peer-deps make it uninstallable

[konsumer]

In a current working project, where I have a current version of react & babel I get this when I try to npm install:

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN react-wordcloud@0.0.1 requires a peer of babel-polyfill@^6.6.1 but none was installed.
npm WARN react-wordcloud@0.0.1 requires a peer of normalize.css@^3.0.3 but none was installed.
npm WARN react-wordcloud@0.0.1 requires a peer of react@^0.14.7 but none was installed.
npm WARN react-wordcloud@0.0.1 requires a peer of react-dom@^0.14.7 but none was installed.

And then the package doesn't resolve on import. Here is my project's dependencies:

"dependencies": {
    "muicss": "^0.9.20",
    "react": "^15.6.1",
    "react-dom": "^15.6.1",
    "react-redux": "^5.0.5",
    "react-scripts": "1.0.10",
    "redux": "^3.7.2",
    "victory": "^0.21.3"
  },
  "devDependencies": {
    "@kadira/storybook": "^2.21.0"
  }

[Purii]

Could you update the peerDependencies and check if the component still works? I will accept a PR 👍

…

Am 31.07.2017 um 23:53 schrieb David Konsumer ***@***.***>: In a current project, where I have a current version of react & babel I get this when I try to npm install: npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN ***@***.*** requires a peer of babel-polyfill@^6.6.1 but none was installed. npm WARN ***@***.*** requires a peer of normalize.css@^3.0.3 but none was installed. npm WARN ***@***.*** requires a peer of react@^0.14.7 but none was installed. npm WARN ***@***.*** requires a peer of react-dom@^0.14.7 but none was installed. And then the package doesn't resolve on import. Here is my project's dependencies: "dependencies": { "muicss": "^0.9.20", "react": "^15.6.1", "react-dom": "^15.6.1", "react-redux": "^5.0.5", "react-scripts": "1.0.10", "redux": "^3.7.2", "victory": "^0.21.3" }, "devDependencies": { ***@***.***/storybook": "^2.21.0" } — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.