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
{{ message }}
This repository has been archived by the owner on Mar 6, 2024. It is now read-only.
Currently, to use vanilla-extract in Storybook, it is necessary to manually rewrite the settings to support it.
If this add-on supports vanilla-extract, it will be more convenient to use vanilla-extract without configuration by using this add-on.
The text was updated successfully, but these errors were encountered:
Wow. That's great.
I look forward to the official release of v2!
Can you tell me more about your project?
What framework are you using?
I often use Next.js for frameworks.
As for styling libraries, I used to use Emotion in the past, but these days I tend to use vanilla-extract.
I am also interested in kuma-ui, but have not used it yet.
It seems there is also a Webpack plugin, so it may be possible to support it with this add-on.
what version of Storybook are you on?
We update our libraries regularly with Renovate, so Storybook is always up-to-date with the latest versions.
To make sure your stories render as expected, storybook mimics the Webpack config of Next. Because of this, we need to find a way for Storybook to apply the changes that @vanilla-extract/next-plugin makes to Next's Webpack.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, to use vanilla-extract in Storybook, it is necessary to manually rewrite the settings to support it.
If this add-on supports vanilla-extract, it will be more convenient to use vanilla-extract without configuration by using this add-on.
The text was updated successfully, but these errors were encountered: