Once upon a time, there was a coder named Dude. He started working at a company that told him they were innovative and that their code was glorious. This was a lie. He murdered everyone.

The End.

To the reactjs-centered fucks who develop the popular web component viewing software called storybook: have you ever heard about semver?
89 alpha/beta/rc releases for a minor update 6.3 -> 6.4 with "100's of fixes and enhancements" "in preparation of the HUGE 7.0 release". Gee I wonder will it have 1000's of bugfixes? How bug-ridden is this software?
Every minor upgrade since 5.x is backwards-incompatible and requires a day of frustration finding out in how many more fucking NPM packages you split your codebase just because it's cool. I know move fast and break things, but some of us have other things to do than resolving node_modules incompatibilities you know. "No just hit 'npx sb upgrade' you say". I did, I really did! And the browser showed a blank screen of death with tons of cryptic React errors, it really did! Thank God you abstracted away all your dependencies in that sb command, now you can't even read the docs about what could have gone wrong with a specific sub-package. You have @storybook/html but the docs redirect to React pages, so good luck if you use something else

This is so sad... like.. the IDEA of storybook is great. But why did faith put the capacity to develop such a tool into the hands of people who think the world centers around React and JSX.. HTML should have been the default, and then you build on top of that for your fav framework, not the other way around

i fucking hate react and don't understand react

Is it cleaner to have useContext to pipe in override test data for storybook and write an outer context for that code only? Real production code can ignore and not set this.

Can child component onHover update parent's stateful variable to unpause the urql/graphql datafetch in parent data wrapper component. Parent pipes queried data to child component to properly display on hover that kicked process off.

So on friday i got a super speed course on how to develop a new styleguide in Angular with Storybook. Superspeed because fellow dev went on vacation for a week. Today is monday and i forgot everything i need to know.

This is gonna be a difficult week :/

Javascript/React question of the day: Habe you used Storybook.js? How was it?

Would you recommend using it in a medium sized side project? (I'm also considering simply using docz)

Has anyone used Storybook for Angular components (or other framework)? Would be interested to hear advantages and disadvantages.

Thanks!

Anyone else having so much problems using create-react-app, typescript, styled-components and storybook?
It fells like im playing the lottery here and most of it doesnt reliable work.

Several months ago I was praising antd's forms but honestly I can't figure how to debug them with React Context Devtools, let alone do that inside React Storybook.

Unless I come up with a solution for this problem I'm a dead man.

Last days i’m digging in the legacy of this company. As if the first styleguide i had to work with wasnt worse enough i found two others now that are using different frameworks and are not part of the deployment process.

So far i had fractal, now busy with patternlab and yesterday foundation and the latest one; storybook.

There is duplicate code everywhere how on earth do they expect me to keep any kind of overview in this freaking mess they made?!