Sharing configs between Storybook and Vite

kzuraw

Krzysztof Żuraw

Posted on May 8, 2023

Sharing configs between Storybook and Vite

I have a project that is using Vite.js as a bundler with Storybook to have visual testing of components. I recently updated Storybook from version 5 to 7. Here are a couple of things I had to do to make it work.

Firstly you have to know that Storybook in version 7 will merge project vite.config.js to its own. What does it mean? It means that all your plugins will work out of the box with Storybook but on the other hand, you need to make sure that your paths in vite.config.js are correct. By correct I mean they should be absolute, not relative. Why? Let's say that you have your vite plugin configured to look for index.tsx file like this: entry: "./index.tsx" - it will work in your project but not in Storybook. It won't work because Storybook will look for index.tsx from its directory (by default in the .storybook folder), not from the root of your project. So you have to make sure that your paths are absolute. How to do this? You can use the path module from Node.js. Here is an example:

import { resolve } from "path";

export default defineConfig({
  plugins: [
    viteHtml({
      entry: resolve(__dirname, "index.tsx"),
    }),
  ],
});
Enter fullscreen mode Exit fullscreen mode

Another issue that I found is that not all plugins will work with Storybook. For example, @vitejs/plugin-react-swc will not work with Storybook 7 - you can see the GitHub issue for details. What you can do to fix this? You can use the solution provided in the issue and remove the plugin from the config when running Storybook. Here is a code example:

import react from "@vitejs/plugin-react";
import { withoutVitePlugins } from "@storybook/builder-vite";

const config = {
  // the rest of the config
  async viteFinal(config) {
    config.plugins = await withoutVitePlugins(config.plugins, [
      "vite:react-swc",
    ]);

    return mergeConfig(config, {
      plugins: [react()],
    });
  },
};
Enter fullscreen mode Exit fullscreen mode

Other than those two issues migrating to Storybook 7 was quite nice. Storybook has even a nice codemod to migrate from storiesOf to the new CSF format. That is all for today and I hope this will help you to migrate your project to Storybook 7.

💖 💪 🙅 🚩
kzuraw
Krzysztof Żuraw

Posted on May 8, 2023

Join Our Newsletter. No Spam, Only the good stuff.

Sign up to receive the latest update from our blog.

Related