new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Storybook · all subjects

contributing/debugging

5 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Reproducing CI job failures locally

After creating a PR, if a CI job fails, the job logs will print a message explaining how to reproduce the task locally. Typically this involves running the task against the right template, e.g., `yarn task --task e2e-tests --template=react-vite/default-ts --start-from=install`. It's recommended to start from the `install` task to ensure local code is completely up to date. After reproducing the failure and making fixes, compile with `build`, then rerun the task with `--start-from=auto`.

CI linked vs unlinked mode behavior

The default instructions run code in 'linked' mode, where built changes to Storybook library code are reflected in the sandbox immediately on the next run. However, CI runs in 'unlinked' mode, which in rare cases behaves differently. If having trouble reproducing a failure, try rerunning the command with the `--no-link` flag. After using `--no-link`, you'll need to run with `--start-from=compile` after each code change.

Troubleshooting Storybook 10 upgrade with doctor command

The doctor command can be used to check for common issues such as duplicate dependencies, incompatible addons, or mismatched versions after upgrading to Storybook 10.

Troubleshooting Storybook 9 upgrade issues with doctor command

The doctor CLI command can be used to check for common issues after upgrading to Storybook 9, such as duplicate dependencies, incompatible addons, or mismatched versions.

Storybook upgrade error debugging

If issues occur during upgrade, a `debug-storybook.log` file is created in the repository root with all relevant logs. Set the log level to `debug` using the `--loglevel debug` flag for more detailed information. You can also use the `--logfile [path]` flag to write all debug logs to a specified file.

Give your agent this brain