What is the future of this project? #494
Comments
|
If I were using this project more actively right now, I'd probably volunteer to help with maintenance, but I worry I won't be able to prioritize it until I pick the work back up that leveraged this package. I'll try to look into this, but does Storybook still use this package actively? I was thinking @chromaui might be a good steward for this project and if they are indeed still using it in Storybook, they'd have a vested interest in keeping things going here. Also, I just want to say thank you again for your contribution to open source with this project @pvasek. Well done with the structure of this codebase :) |
|
Yeah, I'm also curious if someone at Chromatic (@chromaui) would be interested in maintaining it. While I'm actively using this library right now, I'll be transitioning off the project that uses it over the next couple months. I do know that they've changed the Storybook default in v8 to use |
|
I just noticed that at one point @shilman had published a fork of this on npm but that now the repo is archived. Any interested in reviving it and publishing some of the features and fixes in this repo from the past couple years, since you have the infrastructure to publish that package to npm? |
## Description 📝 Performance optimizations for running Storybook locally The main culprit is using `react-docgen-typescript`; it's parsing every file for docgen info. The package is also [no longer being maintained](styleguidist/react-docgen-typescript#494) (the last release was in [end of 2021](https://github.com/styleguidist/react-docgen-typescript/releases)). - There's a faster docgen library that Storybook 8 uses, `react-docgen`, however we're missing a lot of typing by using that since it's using a shallower analysis. - The solution I ended up at was to keep `react-docgen-typescript`, but tighten the scope on what files are parsed for the docgen (Components and Features only). And to also disable `allowSyntheticDefaultImports` and `esModuleInterop` per the [Storybook MUI docs ](https://storybook.js.org/recipes/@mui/material#4-use-material-ui-prop-types-for-better-controls-and-docs) The time from first paint to Intro loaded on my Intel i7 2019 MBP went from `over 1 minute` to `30s` 🎉 ## How to test 🧪 ### Reproduction steps (How to reproduce the issue, if applicable) - On the develop branch, run Storybook locally and time the time it takes from first paint to Intro loaded ### Verification steps (How to verify changes) - Pull down this branch, run Storybook locally and the time from first paint to Intro loaded should be shorter than develop - The should be no regressions in the typing and loading of stories compared to https://design.linode.com/
Hi guys, as you could probably notice. I don't have time and interest to work on it anymore.
As @jrolfs correctly mentioned in PR #473, obviously this project is stalled out.
Is there anyone who is using this project and is interested in becoming a maintainer?
Options:
I guess option 1 would be easier for all who already using it. But there can be a tricky part with transferring npm package rights. Not technically but of course, I would have to trust this guy before doing so.
Option 2 is much easier in this case. I would just update the readme of this project pointing to the new one and that's it.
What are your opinions about it?
The text was updated successfully, but these errors were encountered: