-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
[Bug]: Storybook asks to send Crash report on all errors #22510
Comments
If you respond "n" it shouldn't ask you again until you clear your |
Where is the configuration to turn this off by default? |
I would also like to know where is the configuration to turn this off by default? |
i found it https://storybook.js.org/docs/react/configure/telemetry#crash-reports-disabled-by-default |
broken link above, try: https://storybook.js.org/docs/react/configure/telemetry#crash-reports-disabled-by-default core: {
enableCrashReports: false,
}, |
To disable this prompt entirely add this flag --disable-telemetry https://storybook.js.org/docs/react/configure/telemetry#how-to-opt-out This will prevent the prompt |
We are using turbo build, so the CI doesn't print logs until command failed or succeeded. Took a while to debug that Storybook is the culprit Doing interactive prompts in non-interactive environment (CI machine) is a bug - Storybook should not do that |
@shilman CI machines clear node_modules on each run |
@tmeasday any recollection why we added this extra 'test' clause? |
I don't remember but I assume because we were trying to test the prompting. Perhaps we should use our own env var for this or something,. |
This should be fixed in our upcoming Storybook 8.2 release! |
Describe the bug
When there's an error and we hit ctrl c to fix it and restart, storybook still asks if we want to send a crash report so we have to hit ctrl c again ... It would be nice if it only asked about crash reports when it crashes outside of normal errors:
To Reproduce
No response
System
Additional context
No response
The text was updated successfully, but these errors were encountered: