chore(deps): update storybook
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
@storybook/test-runner | devDependencies | minor | 0.19.1 -> 0.21.0 |
eslint-plugin-storybook | devDependencies | patch | 0.11.1 -> 0.11.2 |
MR created with the help of gitlab-org/frontend/renovate-gitlab-bot
Release Notes
storybookjs/test-runner (@storybook/test-runner)
v0.21.0
🚀 Enhancement
- Release 0.21.0 #527 (@kaelig @guspan-tanadi @yannbf)
- Feature: Add --listTests flag from Jest #521 (@kaelig)
🐛 Bug Fix
- style(README): highlight Markdown Note section #523 (@guspan-tanadi)
- Fix: Handle RSC errors #526 (@yannbf)
Authors: 3
- Guspan Tanadi (@guspan-tanadi)
- Kaelig Deloumeau-Prigent (@kaelig)
- Yann Braga (@yannbf)
v0.20.1
🐛 Bug Fix
Authors: 1
- Yann Braga (@yannbf)
v0.20.0
Release Notes
Refactor: Align with Storybook 8.2 core package layout
This is a structural change that shouldn't really affect you. As long as you have the storybook
dependency in your app (which you should), you're good! This change makes it so that the test-runner deduplicates Storybook dependencies, and therefore, slims down your node_modules size.
#494)
Feature: Run postVisit on failures (The test-runner's postVisit hook now runs even if there are failures. This allows you to, for instance, take snapshots on component failures. You can check whether the test has failed via the hasFailure
property in the context passed to the hook:
const config: TestRunnerConfig = {
async postVisit(_page, context) {
if(context.hasFailure) {
console.log('problems!')
// do a snapshot, write a log, or anything you like
}
},
}
🚀 Enhancement
- Feature: Run postVisit on failures #494 (@yannbf)
- Align with Storybook 8.2 core package layout #512 (@yannbf)
📝 Documentation
Authors: 6
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.