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
We currently have a heavily customised Styleguidist project running using Lerna supporting ~500 components. We're looking at breaking this down a bit so that we can have multiple projects with fewer components, but we'd like to retain the look and feel between these applications.
I was just wondering if there's any way of consuming published components as part of the Styleguide config components object? Currently it looks as though you can only provide a relative path to components, but we would like to be able to publish a package and then import { ThemeProvider } from 'package-name' and pass this in to the components object.
Hello,
We currently have a heavily customised Styleguidist project running using Lerna supporting ~500 components. We're looking at breaking this down a bit so that we can have multiple projects with fewer components, but we'd like to retain the look and feel between these applications.
I was just wondering if there's any way of consuming published components as part of the Styleguide config
components
object? Currently it looks as though you can only provide a relative path to components, but we would like to be able to publish a package and thenimport { ThemeProvider } from 'package-name'
and pass this in to thecomponents
object.Basically something like:
Is this possible? Not sure if something like this - https://react-styleguidist.js.org/docs/cookbook#how-to-change-styles-of-a-style-guide - would already work?
The text was updated successfully, but these errors were encountered: