-
-
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]: Updating from 8.4.7 to 8.5.0 on a webpack setup does not work #30423
Comments
** Disclaimer** This information might be inaccurate, due to it being generated automatically
|
It seems this may be an issue with test-runner: storybookjs/test-runner#536 |
@valentinpalkovic @kasperpeulen I think we should handle this ourselves instead: https://github.com/storybookjs/storybook/blob/next/code/addons/a11y/src/preview.tsx#L58 Or potentially prebundle https://github.com/chaance/vitest-axe/blob/main/src/to-have-no-violations.ts |
@alebrozzo Does 8.6.0-alpha.4 solve your problem? It contains this fix #30439 |
Describe the bug
I have a complex setup that uses Webpack 5.97, and we are using Storybook 8.4.7. I am trying to update to 8.5.0 but I get the following error:
As I said, I am not using vitest but the latest version of webpack. I can see in my packge-lock file that vitest-axe is being installed as a dependency by @storybook/addon-a11y and I see it in my node_modules folder. I have tried manually adding thre reference with no change in the error. I have also tried with storybook v8.5.2 and with Webpack v5.96.
I tried to use AI to fix this and it suggested to set parameters.a11y.config.matcher to null in preview.ts, but that didn't fix the problem either.
I have now updated every other storybook addon to 8.5.2 and left a11y on 8.4.7 and I don't get the error.
Reproduction link
don't have one, the setup is too complex (and private)
Reproduction steps
It's OK if you close this, I find it odd that vitest is a non dev dependency of an addon though and perhaps that is enough of a hint to be able to fix?
System
Additional context
No response
The text was updated successfully, but these errors were encountered: