We adopted @storybookjs at @getsentry about 8 months ago and it's really accelerated how we build UI components: https://github.com/getsentry/sentry/pull/7308 …pic.twitter.com/4bScC2MSBE
-
-
Sure would be nice if storybook stood up a testing storybook for every PR.
2 replies 0 retweets 3 likes -
Replying to @samccone @bentlegen and
Storybook is Neato but having to have an entire parallel Storybook Build System was not super great, in my last project I used it, we had 3 separate transpilation pipelines for Prod+Dev / Test via Jest / Storybook.
1 reply 0 retweets 1 like -
Replying to @anaisbetts @samccone and
(I will admit that the problem certainly could have been me Doing It Wrong though)
1 reply 0 retweets 0 likes -
Replying to @anaisbetts @paulcbetts and
Not sure if this is different, but it's part of our monorepo / main server source code (getsentry/sentry)
1 reply 0 retweets 0 likes -
Replying to @bentlegen @samccone and
Sure, but when you start Storybook, you're going through Storybook's pipeline. If it's similar to your prod one, great! If not, you have a Bad Time
2 replies 0 retweets 0 likes -
Replying to @anaisbetts @paulcbetts and
ideally components would be standalone and build-able independently so you could say storybook run MY_COMPONENT_BUILD_RULE MY_STORY_BOOK_CONFIG /shrug
3 replies 0 retweets 2 likes -
This Tweet is unavailable.
-
ahhhhhhhpic.twitter.com/21tYiiL5ZZ
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 