@storybook/addon-styling-webpack
Get started in Storybook 7 faster with popular styling tools.
β¨ Features
- π€ Zero-config for popular tools through codemods.
- 𧩠Configuration templates for popular tools
- β‘οΈ Options for CSS modules, PostCSS, Sass, Less, and Vanilla-extract
π Getting
π€ Automatic configuration
To get started, install the package using the Storybook CLI:
pnpm:
pnpm dlx storybook@latest add @storybook/addon-styling-webpack
yarn:
yarn dlx storybook@latest add @storybook/addon-styling-webpack
npm:
npx storybook@latest add @storybook/addon-styling-webpack
What does this do?
Under the hood, this installs the package in your project and adds the addon to your main.js
file.
After that, it will run npx @storybook/auto-config styling
. This is a codemod package that will attempt to detect the styling tools in your project and configure your storybook accordingly.
If the codemod fails, please try running npx @storybook/auto-config styling
manually. If that fails, please file an issue in the auto-config repo.
π οΈ Manual configuration
@storybook/addon-styling-webpack
takes Webpack module rules for your styling tools and replaces the existing rules in Storybook's Webpack config. This avoids duplicating rules that will break your Storybook build.
{
name: '@storybook/addon-styling-webpack',
options: {
rules: [
// Replaces existing CSS rules with given rule
{
test: /\.css$/,
use: [
'style-loader',
'css-loader',
],
}
]
}
}
It can also take Webpack plugins to add to the Storybook config.
{
name: '@storybook/addon-styling-webpack',
options: {
plugins: [
new MiniCssExtractPlugin(),
]
}
}
𧩠Popular Configurations
Below are a few popular configurations for common styling tools to get you started. More complex configurations are possible by combining the different rules below.
PostCSS
// Often used for tailwind
{
name: '@storybook/addon-styling-webpack',
options: {
rules: [
// Replaces existing CSS rules to support PostCSS
{
test: /\.css$/,
use: [
'style-loader',
{
loader: 'css-loader',
options: { importLoaders: 1 }
},
{
// Gets options from `postcss.config.js` in your project root
loader: 'postcss-loader',
options: { implementation: require.resolve('postcss') }
}
],
}
]
}
}
You can also take a look at this example project that uses PostCSS for Tailwind with Storybook:
CSS Modules
{
name: '@storybook/addon-styling-webpack',
options: {
rules: [
// Replaces existing CSS rules to support CSS Modules
{
test: /\.css$/,
use: [
'style-loader',
{
loader: 'css-loader',
options: {
modules: {
auto: true,
localIdentName: '[name]__[local]--[hash:base64:5]',
},
},
}
],
}
]
}
}
Sass
{
name: '@storybook/addon-styling-webpack',
options: {
rules: [
// Replaces any existing Sass rules with given rules
{
test: /\.s[ac]ss$/i,
use: [
"style-loader",
"css-loader",
{
loader: "sass-loader",
options: { implementation: require.resolve("sass") }
},
],
},
]
}
}
Less
{
name: '@storybook/addon-styling-webpack',
options: {
rules: [
// Replaces any existing Sass rules with given rules
{
test: /\.less$/i,
use: [
"style-loader",
"css-loader",
{
loader: "less-loader",
options: { implementation: require.resolve("less") }
},
],
},
]
}
}
Vanilla-extract
{
name: '@storybook/addon-styling-webpack',
options: {
plugins: [
new VanillaExtractPlugin(),
new MiniCssExtractPlugin(),
],
rules: [
{
test: /\.css$/,
sideEffects: true,
use: [
require.resolve("style-loader"),
{
loader: require.resolve("css-loader"),
options: {},
},
],
exclude: /\.vanilla\.css$/,
},
{
// Targets only CSS files generated by vanilla-extract
test: /\.vanilla\.css$/i,
sideEffects: true,
use: [
MiniCssExtractPlugin.loader,
{
loader: require.resolve('css-loader'),
options: {
// Required as image imports should be handled via JS/TS import statements
url: false,
},
},
],
},
]
}
}
Troubleshooting
Monorepos are a more advanced setup that may require a bit more configuration. To find out more. Refer to the Storybook FAQs on monorepos.
π€ Contributing
If you'd like to contribute to this addon, THANK YOU, I'd love your help π
π Development scripts
pnpm build
build and package your addon code
π² Branch structure
- next - the
next
version on npm, and the development branch where most work occurs - main - the
latest
version on npm and the stable version that most users use
π Release process
- All PRs should target the
next
branch, which depends on thenext
version of Storybook. - When merged, a new version of this package will be released on the
next
NPM tag. - If the change contains a bugfix that needs to be patched back to the stable version, please note that in PR description.
- PRs labeled
pick
will get cherry-picked back to themain
branch and will generate a release on thelatest
npm tag.
- domyen
- kasperpeulen
- valentinpalkovic
- jreinhold
- kylegach
- ndelangen