chore(deps): update dependency @storybook/test-runner to ^0.24.0 by renovate[bot] · Pull Request #53 · napolab/vite

In Storybook 9, the accessibility addon has been enhanced with automated reporting capabilities and the Test-runner has out of the box support for it. If you have @storybook/addon-a11y installed, as long as you enable them via parameters, you will get a11y checks for every story:

// .storybook/preview.ts

const preview = {
  parameters: {
    a11y: {
      // 'error' will cause a11y violations to fail tests
      test: 'error', // or 'todo' or 'off'
    },
  },
};

export default preview;

If you had a11y tests set up previously for Storybook 8 (using axe-playwright and the test-runner hooks), you can uninstall axe-playwright and remove all the code from the test-runner hooks, as they are not necessary anymore.

🐛 Bug Fix

Add telemetry to test run #566 (@yannbf)
fix a11y report checking bug #562 (@yannbf)
Fix: Support a11y disable parameter #558 (@yannbf)
Replace @storybook/csf with storybook's internal csf implementation #556 (@yannbf)

Authors: 2

Tom Coleman (@tmeasday)
Yann Braga (@yannbf)

`v0.22.1`

Compare Source

🐛 Bug Fix

Patch: Add telemetry to test run #565 (@yannbf)

Authors: 1

Yann Braga (@yannbf)

`v0.22.0`

Compare Source

🚀 Enhancement

Release v0.22.0 #553 (@ronakj @ndelangen @kasperpeulen @yannbf)
Dependencies: Add sb9 alpha compatibility #551 (@ndelangen)

🐛 Bug Fix

Exclude new server component error #552 (@kasperpeulen)

Authors: 4

Kasper Peulen (@kasperpeulen)
Norbert de Langen (@ndelangen)
Ronak Jain (@ronakj)
Yann Braga (@yannbf)

`v0.21.3`

Compare Source

🐛 Bug Fix

fix: Use StoryFinished event if available #548 (@valentinpalkovic)

Authors: 1

Valentin Palkovic (@valentinpalkovic)

`v0.21.2`

Compare Source

🐛 Bug Fix

Revert "Fix a11y compatibility with Storybook 8.5 and above" #546 (@valentinpalkovic)

Authors: 1

Valentin Palkovic (@valentinpalkovic)

`v0.21.1`

Compare Source

🐛 Bug Fix

Fix a11y compatibility with Storybook 8.5 and above #536 (@valentinpalkovic)

Authors: 2

Jeppe Reinhold (@JReinhold)
Valentin Palkovic (@valentinpalkovic)

`v0.21.0`

Compare Source

🚀 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`

Compare Source

🐛 Bug Fix

Release 0.20.1 #520 (@yannbf)
Fix postVisit hook issue #519 (@yannbf)

Authors: 1

Yann Braga (@yannbf)

`v0.20.0`

Compare Source

Release Notes

Feature: Run postVisit on failures (#494)

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

Release 0.20.0 #518 (@yannbf @shilman)
Feature: Run postVisit on failures #494 (@yannbf)
Release 0.20.0 #514 (@yannbf runner@fv-az773-358.an51pne1gm2ejjnmkprpigk40g.dx.internal.cloudapp.net)
Align with Storybook 8.2 core package layout #512 (@yannbf)

📝 Documentation

Fix tags docs #497 (@shilman @yannbf)

Authors: 6

Michael Shilman (@shilman)
shilman (runner@fv-az1567-4.ivwpl3vsblrubjity54i0equac.phxx.internal.cloudapp.net)
shilman (runner@fv-az2031-358.rag0t2s20xiu3oejmeweyzhkrf.bx.internal.cloudapp.net)
shilman (runner@fv-az738-609.ayi0s4js3kfu5apuyubnvt3std.cx.internal.cloudapp.net)
shilman (runner@fv-az773-358.an51pne1gm2ejjnmkprpigk40g.dx.internal.cloudapp.net)
Yann Braga (@yannbf)

`v0.19.1`

Compare Source

🐛 Bug Fix

Release 0.19.1 #493 (@paulgv @yannbf)
fix(deps): upgrade @storybook/csf to v0.1.11 #491 (@paulgv)

Authors: 2

Paul Gascou-Vaillancourt (@paulgv)
Yann Braga (@yannbf)

`v0.19.0`

Compare Source

🚀 Enhancement

Release 0.19.0 #486 (@yannbf filip.witosz+textace@gmail.com @ysgk)
Feat: Add errorMessageFormatter #468 (@yannbf filip.witosz+textace@gmail.com)

🐛 Bug Fix

Fix: Combine tags correctly when transforming story files #485 (@yannbf)
Fix contents of eject functionality #483 (@yannbf)
Unpin @swc/core from 1.5.7 #481 (@ysgk)

Authors: 3

@ysgk
Foxhoundn (@Foxhoundn)
Yann Braga (@yannbf)

`v0.18.2`

Compare Source

🐛 Bug Fix

Release 0.18.2 #476 (@shilman @valentinpalkovic @yannbf)
Fix 8.1.4+ support for v5 index.json #475 (@shilman @yannbf)
Pin @swc/core to 1.5.7 #474 (@shilman)

Authors: 3

Michael Shilman (@shilman)
Valentin Palkovic (@valentinpalkovic)
Yann Braga (@yannbf)

`v0.18.1`

Compare Source

🐛 Bug Fix

Release 0.18.1 #466 (@yannbf)
Fix Windows support in coverage generation #461 (@yannbf)
Fix getStoryContext type #462 (@yannbf)
Fix: Skip requiring a main.js file in index.json mode #464 (@yannbf)

Authors: 1

Yann Braga (@yannbf)

`v0.18.0`

Compare Source

🚀 Enhancement

Release 0.18.0 #458 (@skratchdot @yannbf)
Fix coverage reports, add lcov as extra reporter #456 (@yannbf)

🐛 Bug Fix

add --testTimeout cli option from jest #409 (@skratchdot @yannbf)

Authors: 2

◬ (@skratchdot)
Yann Braga (@yannbf)

`v0.17.0`

Compare Source

🚀 Enhancement

Release 0.17.0 #438 (@JReinhold @shilman @valentinpalkovic @yannbf @ndelangen)
Support Storybook 8 #429 (@yannbf)
Support unhandled rendering errors #421 (@yannbf)

🐛 Bug Fix

Prebundle dependencies #431 (@yannbf)
Update internal example to Storybook 8 #430 (@yannbf)
swap storybook/jest to storybook/test #427 (@ndelangen)
Add PR template #428 (@yannbf)
Fix build step #425 (@valentinpalkovic)
Remove --prerelease from sb upgrade CI #423 (@JReinhold)
Support stories with meta id for permalinking #419 (@yannbf)

📝 Documentation

Docs: Add remark regarding pnp support #432 (@yannbf)
docs: replace postRender(deprecated) with postVisit #418 (@junkisai)

Authors: 6

Jeppe Reinhold (@JReinhold)
Junki Saito (@junkisai)
Michael Shilman (@shilman)
Norbert de Langen (@ndelangen)
Valentin Palkovic (@valentinpalkovic)
Yann Braga (@yannbf)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate · 2024-04-16T14:13:57Z

⚠ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm WARN cli npm v10.5.2 does not support Node.js v16.20.1. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @napolab/typescript@1.0.0
npm WARN Found: vite@4.3.9
npm WARN node_modules/vite
npm WARN   dev vite@"^5.0.12" from the root project
npm WARN   11 more (@joshwooding/vite-plugin-react-docgen-typescript, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer vite@"^2.2.3 || ^3.0.0 || ^4.0.3" from @vanilla-extract/vite-plugin@3.8.2
npm WARN node_modules/@vanilla-extract/vite-plugin
npm WARN   dev @vanilla-extract/vite-plugin@"^3.8.0" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @vitejs/plugin-react@3.1.0
npm WARN Found: vite@5.2.9
npm WARN node_modules/vite
npm WARN   dev vite@"^5.0.12" from the root project
npm WARN   7 more (@joshwooding/vite-plugin-react-docgen-typescript, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer vite@"^4.1.0-beta.0" from @vitejs/plugin-react@3.1.0
npm WARN node_modules/@storybook/react-vite/node_modules/@vitejs/plugin-react
npm WARN   @vitejs/plugin-react@"^3.0.1" from @storybook/react-vite@7.6.12
npm WARN   node_modules/@storybook/react-vite
npm WARN 
npm WARN Conflicting peer dependency: vite@4.5.3
npm WARN node_modules/vite
npm WARN   peer vite@"^4.1.0-beta.0" from @vitejs/plugin-react@3.1.0
npm WARN   node_modules/@storybook/react-vite/node_modules/@vitejs/plugin-react
npm WARN     @vitejs/plugin-react@"^3.0.1" from @storybook/react-vite@7.6.12
npm WARN     node_modules/@storybook/react-vite
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: vite@5.2.9
npm ERR! notsup Not compatible with your version of node/npm: vite@5.2.9
npm ERR! notsup Required: {"node":"^18.0.0 || >=20.0.0"}
npm ERR! notsup Actual:   {"npm":"10.5.2","node":"v16.20.1"}

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-16T14_13_08_609Z-debug-0.log

File name: pnpm-lock.yaml

ERROR: This version of pnpm requires at least Node.js v18.12
The current version of Node.js is v16.20.1
Visit https://r.pnpm.io/comp to see the list of past pnpm versions with respective Node.js version support.

renovate · 2024-05-09T11:54:38Z

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @napolab/typescript@1.0.0
npm ERR! Found: storybook@7.6.24
npm ERR! node_modules/storybook
npm ERR!   dev storybook@"^7.0.9" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer storybook@"^0.0.0-0 || ^10.0.0 || ^10.0.0-0 || ^10.1.0-0 || ^10.2.0-0 || ^10.3.0-0 || ^10.4.0-0" from @storybook/test-runner@0.24.3
npm ERR! node_modules/@storybook/test-runner
npm ERR!   dev @storybook/test-runner@"^0.24.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-04-01T17_47_59_859Z-debug-0.log

File name: pnpm-lock.yaml

Progress: resolved 0, reused 1, downloaded 0, added 0
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

This error happened while installing a direct dependency of /tmp/renovate/repos/github/napolab/vite

Your Node version is incompatible with "registry.npmjs.org/@storybook/test-runner/0.24.3".

Expected version: >=20.0.0
Got: v16.20.1

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.

renovate bot force-pushed the renovate/storybook-test-runner-0.x branch from da68a20 to 0c34661 Compare May 9, 2024 11:54

renovate bot changed the title ~~chore(deps): update dependency @storybook/test-runner to ^0.17.0~~ chore(deps): update dependency @storybook/test-runner to ^0.18.0 May 9, 2024

renovate bot force-pushed the renovate/storybook-test-runner-0.x branch from 0c34661 to 110185e Compare June 22, 2024 14:04

renovate bot changed the title ~~chore(deps): update dependency @storybook/test-runner to ^0.18.0~~ chore(deps): update dependency @storybook/test-runner to ^0.19.0 Jun 22, 2024

renovate bot force-pushed the renovate/storybook-test-runner-0.x branch from 110185e to fc1c3e9 Compare November 28, 2024 13:43

renovate bot changed the title ~~chore(deps): update dependency @storybook/test-runner to ^0.19.0~~ chore(deps): update dependency @storybook/test-runner to ^0.20.0 Nov 28, 2024

renovate bot force-pushed the renovate/storybook-test-runner-0.x branch from fc1c3e9 to a353f23 Compare December 20, 2024 12:04

renovate bot changed the title ~~chore(deps): update dependency @storybook/test-runner to ^0.20.0~~ chore(deps): update dependency @storybook/test-runner to ^0.21.0 Dec 20, 2024

renovate bot force-pushed the renovate/storybook-test-runner-0.x branch from a353f23 to 703ccde Compare February 28, 2025 11:15

renovate bot changed the title ~~chore(deps): update dependency @storybook/test-runner to ^0.21.0~~ chore(deps): update dependency @storybook/test-runner to ^0.22.0 Feb 28, 2025

renovate bot force-pushed the renovate/storybook-test-runner-0.x branch from 703ccde to 171e058 Compare June 11, 2025 19:08

renovate bot changed the title ~~chore(deps): update dependency @storybook/test-runner to ^0.22.0~~ chore(deps): update dependency @storybook/test-runner to ^0.23.0 Jun 11, 2025

chore(deps): update dependency @storybook/test-runner to ^0.24.0

daa957e

renovate bot force-pushed the renovate/storybook-test-runner-0.x branch from 171e058 to daa957e Compare October 28, 2025 22:15

renovate bot changed the title ~~chore(deps): update dependency @storybook/test-runner to ^0.23.0~~ chore(deps): update dependency @storybook/test-runner to ^0.24.0 Oct 28, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency @storybook/test-runner to ^0.24.0#53

chore(deps): update dependency @storybook/test-runner to ^0.24.0#53
renovate[bot] wants to merge 1 commit intomainfrom
renovate/storybook-test-runner-0.x

renovate bot commented Apr 16, 2024 •

edited

Loading

Uh oh!

renovate bot commented Apr 16, 2024

Uh oh!

renovate bot commented May 9, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate bot commented Apr 16, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

🐛 Bug Fix

Authors: 1

🐛 Bug Fix

Authors: 1

🐛 Bug Fix

Authors: 3

🚀 Enhancement

🐛 Bug Fix

Authors: 3

🚀 Enhancement

🐛 Bug Fix

Authors: 2

🐛 Bug Fix

Authors: 1

🚀 Enhancement

🐛 Bug Fix

Authors: 4

🐛 Bug Fix

Authors: 1

🐛 Bug Fix

Authors: 1

🐛 Bug Fix

Authors: 2

🚀 Enhancement

🐛 Bug Fix

Authors: 3

🐛 Bug Fix

Authors: 1

Release Notes

Feature: Run postVisit on failures (#​494)

🚀 Enhancement

📝 Documentation

Authors: 6

🐛 Bug Fix

Authors: 2

🚀 Enhancement

🐛 Bug Fix

Authors: 3

🐛 Bug Fix

Authors: 3

🐛 Bug Fix

Authors: 1

🚀 Enhancement

🐛 Bug Fix

Authors: 2

🚀 Enhancement

🐛 Bug Fix

📝 Documentation

Authors: 6

Configuration

Uh oh!

renovate bot commented Apr 16, 2024

⚠ Artifact update problem

File name: package-lock.json

File name: pnpm-lock.yaml

Uh oh!

renovate bot commented May 9, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Artifact update problem

File name: package-lock.json

File name: pnpm-lock.yaml

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Apr 16, 2024 •

edited

Loading

Feature: Run postVisit on failures (#494)

renovate bot commented May 9, 2024 •

edited

Loading