Open hoovercj opened 8 months ago
To give some additional context, I tested this with a fresh install of the latest stable Storybook version and it's happening as well. @yannbf when you have a moment, can you provide some context on this and how best to address it? Thanks in advance.
same here
we are unable to use a custom reporter in the ejected jest configuration
Describe the bug
First reported here: https://github.com/storybookjs/storybook/discussions/25003
I am unable to run storybook tests with a custom test runner.
Note: We use this reporter in our normal jest tests within the same project without problem
Following these instructions
I have ejected and modified the config as follows:
But when running the tests, I get this error:
System Please paste the results of
npx storybook@latest info
here.System: OS: Windows 11 10.0.22621 CPU: (8) x64 Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz Binaries: Node: 16.14.0 - C:\Program Files\nodejs\node.EXE npm: 8.3.1 - C:\Program Files\nodejs\npm.CMD <----- active Browsers: Edge: Chromium (119.0.2151.72) npmPackages: @storybook/addon-a11y: 6.5.16 => 6.5.16 @storybook/addon-actions: 6.5.16 => 6.5.16 @storybook/addon-essentials: 6.5.16 => 6.5.16 @storybook/addon-interactions: 6.5.16 => 6.5.16 @storybook/addon-links: 6.5.16 => 6.5.16 @storybook/addon-postcss: 2.0.0 => 2.0.0 @storybook/addon-storyshots: 6.5.16 => 6.5.16 @storybook/addon-storysource: 6.5.16 => 6.5.16 @storybook/builder-webpack5: 6.5.16 => 6.5.16 @storybook/jest: 0.2.2 => 0.2.2 @storybook/manager-webpack5: 6.5.16 => 6.5.16 @storybook/react: 6.5.16 => 6.5.16 @storybook/test-runner: 0.15.2 => 0.15.2 @storybook/testing-library: 0.2.2 => 0.2.2 storybook-addon-designs: 6.2.1 => 6.2.1 storybook-dark-mode: 1.0.8 => 1.0.8