I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
Thanks for all your work on this OSS product. A couple of questions...
Is Arunoda still working on Storybook, or is he full-time at Zeit?
I'm curious if you'd be considering creating other default setups for Storybook?
There's Vue, React and Angular. Would you consider something like Preact? I've done it by installing the React Storybook then just adding the preact-compats, and it works pretty well, but maybe for new comers, it could help them out if they show an interest in using Preact.
Also, we use Storybook at work with TypeScript/React and we've used the custom webpack.config to get things working to our liking. I wonder as well in a scenario like this, would you consider a default setup for say TypeScript/React or TypeScript/Angular?
A big advantage to Storybook is that we support many different frameworks and configurations. It is also a lot of work and time to develop, test, and support the full customization of every configuration possible on every platform.
We've definitely discussed this and the solution is perhaps allow some less popular combinations of frameworks and configurations to owned and maintained by the community. There are some work we have to do to modularize these configs to enable this.
Arunoda is full-time at Zeit, but he's still a project VIP and has the most commits of any human involved in the project (and I don't think any of us are going to catch up with dependencies.io at this point):
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
He's super nice and helpful. He read over a presentation I did on Storybook a while back. If you're interested, it's at story.iamdeveloper.com. Probably a little out of date though ;)
So we're already kinda compatible with Preact via the method you just described.
I wonder how many preact users are there that would not be comfortable with the needed changes, do you recon it's worth the effort? (including maintenance).
One thing one of our maintainers Igor Davydkin came up with recently was the concept of 'presets' and examples you can clone to get started.
I think this would help in your use-case, as at the very least the process of adopting storybook for Preact is in that case very well documented, because there's a runnable example available.
We could add a Preact version to our CLI too. sounds like a very good first-pr, wanna help?
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
I haven't had time to look into this yet, but I documented the process of how to do it for the time being by installing React first as I mentioned in another comment.
Thanks for all your work on this OSS product. A couple of questions...
Is Arunoda still working on Storybook, or is he full-time at Zeit?
I'm curious if you'd be considering creating other default setups for Storybook?
There's Vue, React and Angular. Would you consider something like Preact? I've done it by installing the React Storybook then just adding the preact-compats, and it works pretty well, but maybe for new comers, it could help them out if they show an interest in using Preact.
Also, we use Storybook at work with TypeScript/React and we've used the custom webpack.config to get things working to our liking. I wonder as well in a scenario like this, would you consider a default setup for say TypeScript/React or TypeScript/Angular?
Arunoda is still an admin on the project and stuff, but he's gone to focus on other things.
A big advantage to Storybook is that we support many different frameworks and configurations. It is also a lot of work and time to develop, test, and support the full customization of every configuration possible on every platform.
We've definitely discussed this and the solution is perhaps allow some less popular combinations of frameworks and configurations to owned and maintained by the community. There are some work we have to do to modularize these configs to enable this.
Arunoda is full-time at Zeit, but he's still a project VIP and has the most commits of any human involved in the project (and I don't think any of us are going to catch up with dependencies.io at this point):
github.com/storybooks/storybook/gr...
He's super nice and helpful. He read over a presentation I did on Storybook a while back. If you're interested, it's at story.iamdeveloper.com. Probably a little out of date though ;)
So we're already kinda compatible with Preact via the method you just described.
I wonder how many preact users are there that would not be comfortable with the needed changes, do you recon it's worth the effort? (including maintenance).
One thing one of our maintainers Igor Davydkin came up with recently was the concept of 'presets' and examples you can clone to get started.
I think this would help in your use-case, as at the very least the process of adopting storybook for Preact is in that case very well documented, because there's a runnable example available.
We could add a Preact version to our CLI too. sounds like a very good first-pr, wanna help?
Sure, np. Would love to help out.
I haven't had time to look into this yet, but I documented the process of how to do it for the time being by installing React first as I mentioned in another comment.
Setting up Storybook for Preact
Nick Taylor
Yes we want to make TypeScript usage with Storybook seamless soon!