Just look at the open issues counters for "state-of-the-art" "production-ready" JS packages:

https://github.com/storybookjs/....
Almost 1900.
https://github.com/vercel/next.js
More than 1200.

It's just depressing

JavaScript is the most toxic language because of the community.

I bet at least 25% of those issues are just flame cards bitching about something that's clearly documented but they never RTFM.

@sariel You're absolutely right. The first issue on Storybook is literary "I can't have different major versions of Storybook in the same repository", like no shit Sherlock, that's exactly what major versions mean.

Storybook has an absurdly large dependency tree and all of it is outdated as fuck. The only way to use it without effectively generating a special list of bugs that only appear in the storybook build, is to make sure you don't use anything Storybook uses - apart from the framework of choice ofc - especially not build tools.

Let me repeat that, it's so old you get less bugs by maintaining two build chains than by trying to work with the versions storybook uses outside storybook.

Wow 1129 of the 1900 issues are labeled as bugs 😬