-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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 warnings #2303
Comments
I'm not sure that we should be maintaining
@Hypnosphi you've been dealing with a lot of dependencies. Thoughts? |
I'd vote for replacing komposer/podda/mantra stack with redux. @alexandrebodin even started doing it in a branch some time ago |
I'm still intrigued about |
I think a good temporary measure would be to fork the old mantra, komposer, podda repos over and publish a React 16 version with minor bug fixes. I'd be willing to do it if it's something we want. |
@danielduan yeah, sounds like a great plan. Actually you can start with just changing their peerDeps, given that things seem to work well with React 16 as is |
I'd love to be able to push out some updates of those packages, unfortunately some appear abandoned. |
We should still investigate the storyshots dependencies though. |
Nice work! Now down to these warnings:
|
I get that peer dependencies reduce the amount of packages installed, but I don't think the rest of these need to be. React is one thing because you can't share an instance of react or else it will cause problems.
|
As for |
Is there anything we can do about the babel ones? If not, we can just close this ticket and say the rest of those can't really be fixed. |
We already have |
BTW, here is the relevant (I think) yarn bug: yarnpkg/yarn#2688 (comment) |
I wonder if a transitive dependency counts as a peer dependency in yarn's definition in general. I'm gonna close this ticket so we can worry about more important things. This issue is not 100% fixed, but good enough I think. If anyone has a fix and would like to help out, please comment and open a PR. |
Can these just be removed from |
@pelotom which of them do you mean exactly? We’re only in control of the ones in |
@Hypnosphi I believe you that they're relevant, but can't they just be regular dependencies? I'd rather not pollute the top-level dependencies of my app with things that only storybook needs. |
We really need a single instance of |
Also related would be the use of react-transition-group (present libraries are using version 1, whereas version 2 is available). |
Any news on this front? I've added a dependency on
I'm currently on |
Actually this is the reason why we need |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 60 days. Thanks! |
Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook! |
it would be nice, if you could clean the peer dependencies again :) warning "@storybook/addon-a11y > @storybook/components@5.1.7" has unmet peer dependency "react-dom@*".
warning "@storybook/addon-a11y > @storybook/theming@5.1.7" has unmet peer dependency "react-dom@*".
warning "@storybook/addon-a11y > react-sizeme@2.6.7" has unmet peer dependency "prop-types@^15.0.0-0".
warning "@storybook/addon-a11y > react-sizeme@2.6.7" has unmet peer dependency "react-dom@^0.14.0 || ^15.0.0-0 || ^16.0.0".
warning "@storybook/addon-notes > markdown-to-jsx@6.10.2" has unmet peer dependency "react@>= 0.14.0".
warning "@storybook/addon-a11y > @storybook/api > @storybook/router@5.1.4" has unmet peer dependency "react-dom@*".
warning "@storybook/addon-a11y > @storybook/api > @storybook/router > @reach/router@1.2.1" has unmet peer dependency "react-dom@15.x || 16.x || 16.4.0-alpha.0911da3".
warning "@storybook/addon-a11y > @storybook/api > @storybook/theming@5.1.4" has unmet peer dependency "react-dom@*".
warning " > @storybook/addon-console@1.1.0" has unmet peer dependency "prop-types@*".
warning " > @storybook/addon-console@1.1.0" has unmet peer dependency "react@*".
warning " > @storybook/addon-knobs@5.1.7" has unmet peer dependency "react@*".
warning "@storybook/addon-knobs > react-select@2.4.4" has unmet peer dependency "react@^15.3.0 || ^16.0.0".
warning "@storybook/addon-knobs > react-select@2.4.4" has unmet peer dependency "react-dom@^15.3.0 || ^16.0.0".
warning "@storybook/addon-links > @storybook/router@5.1.7" has unmet peer dependency "react@*".
warning "@storybook/addon-links > @storybook/router@5.1.7" has unmet peer dependency "react-dom@*".
warning "@storybook/addon-knobs > react-color > @icons/material@0.2.4" has unmet peer dependency "react@*".
warning "@storybook/addon-knobs > react-select > react-input-autosize@2.2.1" has unmet peer dependency "react@^0.14.9 || ^15.3.0 || ^16.0.0-rc || ^16.0".
warning "@storybook/addon-knobs > react-select > react-transition-group@2.9.0" has unmet peer dependency "react@>=15.0.0".
warning "@storybook/addon-knobs > react-select > react-transition-group@2.9.0" has unmet peer dependency "react-dom@>=15.0.0".
warning " > @storybook/addon-links@5.1.7" has unmet peer dependency "react@*".
warning " > @storybook/addon-notes@5.1.7" has unmet peer dependency "react@*".
warning " > @storybook/addon-options@5.1.7" has unmet peer dependency "react@*".
warning " > @storybook/addon-viewport@5.1.7" has unmet peer dependency "react@*".
warning "@storybook/vue > @storybook/core@5.1.7" has unmet peer dependency "react@*".
warning "@storybook/vue > @storybook/core@5.1.7" has unmet peer dependency "react-dom@*". |
But Storybook UI (stories tree, addon panels) does. Please install the missing dependencies on your side as |
If Storybook UI requires React, and can be used on projects that are not React, shouldn't it be added as a dependency not a peer dependency? Or perhaps an optional dependency? |
Actually, right now it is: @ndelangen @shilman do you think that we can remove peer dependencies on React from manager-side packages, given that manager uses its own verion of React anyway? |
YES |
Currently I'm getting a bunch of warnings due to storybook when I install dependencies:
A few of these are due to
react-komposer
andreact-simple-di
not allowing React 16 as a peer dependency. These projects each have multiple open issues and PRs to fix these peer dependencies, but no one is responding; they seem to be unmaintained. Would it be possible to either transfer ownership of these projects understorybooks
, or else inline needed functionality that they provide?The others I'm not sure why they are necessary. Why do I need to add a dependency on
babel-core
, for example, when I used TypeScript exclusively and storybook functions just fine? Perhaps some of these things should just bedependencies
/devDependencies
rather thanpeerDependencies
.The text was updated successfully, but these errors were encountered: