Sorry, but you either have no stories or none are selected somehow.
If the problem persists, check the browser console, or the terminal you've run Storybook from.
This component library is agnostic to any framework. All the styling is done in vanilla SCSS. However there are a few important gotchas you need to be aware of.
There are two ways to solve the problem of dependency styling being unloaded. The first is the recommended way, the second is a more labor intensive way that results in a slightly smaller production bundle.
IFCThemeProvider and wrap your project in the theme provider. We talk more about
what this does further down, but the short and sweet version is that the ThemeProvider provides a SCSS file that has
all the SCSS files for all the components imported, so no matter which component you import, the ThemeProvider will have
styling for it and all it's dependencies.import their styling.)The IFCThemeProvider does two important jobs.
theme--default or theme--dark to toggle dark mode and light mode (how this is
implemented will be discussed below). All descendent components draw the styling based on whether they are a child of
theme--default or theme--dark.In the _colors.scss partial file, there is a map that contains two themes, default and dark. The themes must
be symmetrical to avoid issues, but there is no way for me to programmatically enforce that. You as the maintainer
must be disciplined and keep that consistent. When a component wants to style itself with a color that is dark mode or
light mode theme dependent, it utilizes a mixin themed() that is defined in the same file, which causes the styling to
be depedent on the active theme (essentially it does something like .theme--default .ThemedComponent {color: black})
and .theme--dark .ThemedComponent {color: white} in the CSS)
The themed() mixin provides access to a SCSS function called retrieveColor which a consumer downstream uses to
retrieve a color from the currently active map (default or dark). At transpile time, the retrieveColor generates two
stylings as demonstrated above, branched by default and dark. This allows the entire styling to change just based on
the ThemeProvider, without having to change classes for all descendent components.
When you're developing your components, I'd recommend keeping several things in mind.
_colors.scss partial, and import the partial at the top of the Vue SFC style tag as such:<style> tag in your Vue SFC unless you intend for it only to be loaded if the
component itself is loaded directly by the developer consuming this library.Instead you should write a separate MyComponent.scss file which you can then @import into your Vue SFC <style>
area. The reason you should do this is because you'll also want to import your scss file in the ThemeProvider/theme.scss
file so that components that use your component as a dependency have your component style loaded by ThemeProvider.