Why is react stated as peerDependency when using @storybook/vue?
See original GitHub issueI’m using the latest beta version right now (37), and use rush + pnpm for our mono-repo. I can’t find in the docs what the reason is that react is stated as peerDependency for @storybook/vue, and some plugins, while react is only used internally by Storybook. An explanation would be great, as right now, I change them to normal dependency in pnpmfile
, and all still works.
As a side-note: I know it’s not always easy specifying dependencies, and peerDependencies are somewhat over-used out there, while they should only be used when a package really is a plugin/addon, or is suppose to work together with the actual source code and it’s framework.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Understanding Peer Dependencies in JavaScript
When to use peerDependencies? Peer dependencies really come into play when you're developing code that will be used by others, ...
Read more >Using StorybookJS in a component library package with ...
The package. json is using react and react-dom as peer dependencies because I only want to ship code for components only. This package...
Read more >@storybook/react | Yarn - Package Manager
Fast, reliable, and secure dependency management.
Read more >Storybook for Vue
You may have tried to use our quick start guide to setup your project for Storybook. ... Add @storybook/vue; Add vue and babel-core;...
Read more >storybook/vue
Vite: Make vite a peer dependency, update plugins #20281 ... Build: compile detection was using a non-conforming package, causing cache to miss always....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, however this can be updated.
Idea was to move all CLI’s to a single script, all frameworks relied on the same set of addons, then we added essentials and finally starting to migrate popular frameworks using this superset.
There are still some frameworks that are using addon-actions the old way. Instead of excluding this addon from migrated frameworks, we leaved it as is.
Work must go on 🧑🎤
While using Vue.js (CLI) or Nuxt.js, I don’t want to get bothered by any dependency which doesn’t fit to my (selected) stack…