You probably know this story.
Hmmm… I think I’d like to use Storybook to build and test my components in relative isolation.–me, every time I start a new project
(BTW, if you don’t know what Storybook is, the 2-ish minute video below gives a pretty decent overview.) So you go to install it and you find that one or more of the following things has happened since the last time you did this:
- There’s a new version of Storybook
- There’s a new version of Vuetify
- There’s a new version of (node|ecmascript|vue|shiny-new-best-practice)
And of course, even if you have a perfectly valid working version of Storybook already configured in your last project–it doesn’t work anymore. 🙁
And of course, enough time has passed that you don’t really remember the details of why you configured it the way you did the last time, so you have to spend most of a day re-learning it to figure out how to make it work again. How many actual components could you actually have built in that same span of time? Who knows, but we <3 progress.
So, in the vain hope that it won’t change too much between this time and the next time, here’s my latest stab at configuring Storybook to work with Vue and Vuetify. The following assumes you’ve already got a working Vue+Vuetify app created.
Install Storybook + Addons
So far so good. This new installer automatically figures out I’m using Vue and sets me up for that. The a11y (accessibility) plugin is for reminding me to implement, well, accessibility features into my components. The other two are just so I can get the cool dark theme in the Storybook UI.
Go to the dark side
To get the Storybook UI to display in dark mode add this file to the config directory:
This is totally unnecessary, but I’ve found I like dark themes in the apps I use a lot…
These updates get made to the
The trickiest part is getting the SASS rule typed in correctly. Note that if I decide to switch to SCSS or to save the
variables.sass file in a different directory (must be either
sass|scss|styles), I need to update this rule to match. Also, if using SCSS, then I might not need the
indentedSyntax rule. I dunno. I almost always have to look this up, and it always seems to take forever to find the docs.
Wrap It Up
This was new. Last time I followed John Leider’s approach and created a custom add-on with a decorator to wrap all my component stories in Vuetify clothing. However, this repo has been archived. Shit, now that I’m writing this, I realize there’s a new version of that plugin. No matter, it appears the plugin is designed for the old version of Storybook (5.x).
The newer version of Storybook (6.x) lets you put a “decorator” right in the
.storybook/preview.js file. You could probably do that before. There’s probably a more elegant way to do this, but I’m slowly, slowly learning that working code is better than perfect code. Here’s my wrapper:
watch sections of my wrapper are there so you can toggle between languages (i18n) and the dark|light themes when viewing your components in Storybook. If you have other app-level settings you’d like to be able to mess with while building/testing your components, you should put them here.
In order for the above decorator to work, you have to set up your core Vuetify options so that they are exported as an object. Here’s how I do it:
Doing it this way allows you to re-use the options in your Storybook config. That way, if you change your app’s options, they will automatically be reflected in Storybook.
Help is on the way
I borrowed this style of creating stories from John’s plugin. I modified it this time to simplify and flatten the structure needed to generate docs from stories. This file could really go almost anywhere, but this seems like a decent location.
A First Story
With the above helper in place, your stories can look something like:
What the Font!?!
The fonts I specified in
src/sass/variables.sass aren’t showing up! Here’s my SASS:
Oh! Right, I need to create a
preview-head.html so they’ll be imported:
This is basically the same as the old version of Storybook.
That’s about it!
God I hope this configuration info is still relevant by the time I start y next project!! Even though Vue 3 has just been launched, I suspect that won’t be too much of a problem. Of course, Storybook 7 is probably less than a year away. Not to mention that the Vuetify team is bearing down on Vuetify 3. I expect that in a couple of months.
Such is the life of a developer these days. Hope this will be useful to someone. Get it while it’s hot!