You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR! peer react@"*" from @storybook/[email protected]
npm ERR! node_modules/@storybook/addon-viewport
npm ERR! dev @storybook/addon-viewport@"^5.0.6" from the root project
npm ERR! peer react@"*" from @storybook/[email protected]
npm ERR! node_modules/@storybook/components
npm ERR! @storybook/components@"5.0.6" from @storybook/[email protected]
npm ERR! node_modules/@storybook/addon-viewport
npm ERR! dev @storybook/addon-viewport@"^5.0.6" from the root project
npm ERR! 3 more (react-dom, @storybook/theming, @storybook/router)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.0.0 || ^16.0.0" from [email protected]
npm ERR! node_modules/@storybook/components/node_modules/react-focus-lock
npm ERR! react-focus-lock@"^1.17.7" from @storybook/[email protected]
npm ERR! node_modules/@storybook/components
npm ERR! @storybook/components@"5.0.6" from @storybook/[email protected]
npm ERR! node_modules/@storybook/addon-viewport
npm ERR! dev @storybook/addon-viewport@"^5.0.6" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
It will be nice to reduce the number of Javascript dependencies to make them easier to manage. Also having a some kind of bot in the repo for keeping dependencies up to date and CI/CD should help.
Current "master" FTBFS in
npm install
as follows:npm install --legacy-peer-deps
succeeds...The text was updated successfully, but these errors were encountered: