Official SolidJS Integration?

[kachurun]

Hi!
We have a community integration with SolidJS (https://github.com/storybookjs/solidjs), but it's literally broken, there's no documentation and most people just aren't able to make it work. There are also a number of issues with it, autodoc doesn't work, there are some test issues, etc.

Half a year ago I somehow managed to get it working in my project with Storybook 8.4, but it was a pain, and now I can't update it though. A couple days ago I needed to get the storybook up again in another project and I still couldn't get it to work.

So I forked this code, fixed the build and published my own packages:
Framework:
@kachurun/storybook-solid-vite

Renderer:
@kachurun/storybook-solid

And also a simple solution to roll out a clean working Storybook for SolidJS with a single command:
create-solid-storybook

Demo on Stackblitz

---

I am planning to develop this project and I have a question, is it possible to do it officially in official scoping?

I would like to have these packages as @storybook/solidjs and @storybook/solidjs-vite

I'm ready to take responsibility for maintaining this.

[CathalMullan]

I've also been using an unpublished fork of the community integration due to the issues mentioned above.

In terms of maintenance, it was fairly easy to update to support Storybook 9.
Most confusing part was understanding the build system.

In general, seems like the SolidJS integration can just copy the approach of the React integration.
A lot of the types can just be copied over directly and renamed.

If the Storybook team doesn't have the bandwidth to maintain it, maybe moving it under @solidjs-community would be a better solution.

[vanessayuenn]

Thanks so much for bringing this up, and even more for being willing to take on the work. It really means a lot when folks in the community step forward like this.

To be totally transparent: the Storybook team just doesn’t have the capacity right now to maintain framework integrations beyond the core ones. It’s not just Solid — we’re starting to recognize that the best way to support the long tail of frameworks is by leaning more on community-led efforts. Your timing is spot on, and your offer is incredibly appreciated.

We’d fully support you taking this on under your own GitHub and npm org, or if you prefer, following @CathalMullan’s suggestion to publish it under the @solidjs-community umbrella. That way, you can maintain full autonomy over the project and make decisions quickly without being bottlenecked by Storybook’s core release cycles or roadmap priorities. We’d also be happy to archive the existing storybookjs/solidjs repo and update its README to point to your maintained fork, so that the community knows where to go for an up-to-date version.

Let us know how you’d like to proceed. And thank you once again.

[kachurun]

Yeah, that's a great idea, but what are the next steps, guys?
I'm going to support this anyway, so I can officially maintain storybook-storybook, no matter the namespace. The only thing I'd like is to be able to release updates quickly, without having to wait months. That's the only reason I didn't make changes to the original community pack. There are already a number of PRs hanging out there, and no one to accept them.

Today, I will finish version 9 and publish it under the "next" tag in my packages, and deal with autodocs and test support.

[vanessayuenn]

Sounds like the next step is for your to publish the package and transfer the fork under @solidjs-community. Let me know when that's ready and I can update the readme to point to your package and fork.

[jer3m01]

I think moving it to @solidjs-community is a good idea.
Happy to help maintainance.

If you want to discuss in our Discord we should be able to get moving soon.

For autodoc, I've recently published solid-docgen with Storybook in mind.
Is there someone from the @storybookjs team we can get in touch in case we need help/advice?

[kachurun]

That's great, man! I'll use it in my integration

[vanessayuenn]

You can reach out to the Storybook core team on our Discord server.