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
Want to get your input to the topic on how big this problem is and if there are any solution.
This issue affects packages that share configs. Every plugins/addons defined in the shared config should be a peer dependency and it should be available to storybook in the consuming project.
The current behavior is that the peer dependencies are installed like regular dependencies. Under pnpm link-based architecture, storybook is not able to load them, making the auto-peers-install useless or even harmful (by creating duplicate or version conflict).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I have create this discussion in
pnpm
: https://github.com/orgs/pnpm/discussions/8800Want to get your input to the topic on how big this problem is and if there are any solution.
This issue affects packages that share configs. Every plugins/addons defined in the shared config should be a peer dependency and it should be available to
storybook
in the consuming project.The current behavior is that the peer dependencies are installed like regular dependencies. Under
pnpm
link-based architecture,storybook
is not able to load them, making theauto-peers-install
useless or even harmful (by creating duplicate or version conflict).Beta Was this translation helpful? Give feedback.
All reactions