-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Storybook fully recompiles on file change #149
Comments
Could you provide a minimal reproduction and the repeat path please? And how do you recognize that all the files are recompiled (under the hood, in Rspack architecture, you could say they're recompile and that is by design). |
@fi3ework So, I started digging with Rsdoctor, and my initial assumption was wrong. Sometimes, it just stuck for an unreasonable amount of time on several files. Could it be connected to this one? I am not sure about reproduction. I have cloned the storybook-rebuild repo, and with minimal examples, it works fine. Also, I use modern.js for medium-sized projects and don't have issues there, only with Storybook. |
@kirillbashtenko Does this workaround also works for you web-infra-dev/rspack#7490 (comment)? |
@fi3ework No, unfortunately, no. What else we can try or debug? |
You could try to remove the following code I guess, I don't know what it does. - transform: {
- "^.+\\.(t|j)sx?$": "@swc/jest",
- }, And, TBH, I'm not sure what caused the issue, it's weird that takes swc-loader so much time. Could you provide a minimal reproduction if possible (It's okay if it's not small enough, as long as it can be reproduced) |
@fi3ework invited you in a repo ( made it private in case I missed something company-related, but it should generally be good). |
I'll check it later today. |
@fi3ework any luck? is it reproducible for you? |
bump |
Hi, not sure if it's exactly rsbuild issue, but for me when I save one file it recompiles all of them, considering 55 packages it's quite some time. I tried the Vite plugin for the storybook, and it only updates the affected file.
Thank you!
The text was updated successfully, but these errors were encountered: