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
storybook is starting to depend on new versions of react/react-dom than we want to develop against (we want to support a wider range of versions than the latest).
this make it hard to install storybook and the version of react we want in the same package.
if we move storybook to its own app, it can use whatever deps it likes while we continue to develop the source packages at the lowest version of react we support.
this has a second benefit, in that storybook becomes a de facto consumer of source, rather than can of component unit test.
this will give us a much truer picture of what we're exporting, and removes a footgun for contributors whereby exports that have not been added will not available to storybook (e.g. #1653 (review))
The content you are editing has changed. Please copy your edits and refresh the page.
storybook is starting to depend on new versions of react/react-dom than we want to develop against (we want to support a wider range of versions than the latest).
this make it hard to install storybook and the version of react we want in the same package.
if we move storybook to its own app, it can use whatever deps it likes while we continue to develop the source packages at the lowest version of react we support.
this has a second benefit, in that storybook becomes a de facto consumer of source, rather than can of component unit test.
this will give us a much truer picture of what we're exporting, and removes a footgun for contributors whereby exports that have not been added will not available to storybook (e.g. #1653 (review))
Tasks
The text was updated successfully, but these errors were encountered: