Storybook server will rebuild when a storyshots-puppeteer test case fail

[christopher-francisco]

Describe the bug
When one of my storyshots-puppeteer test cases fail, the storybook server prints an extra

webpack building...
webpack built f26cd79228857e78fd4c in 510ms

I believe this might be just that the storybook server is watching for changes in all of the files, including the ones on __image_snapshots__/__diff_output__/. ?

As a result, my test suite isn't being ran successfully, it crashes with this OOM error. Maybe some kind of watch loop?

To Reproduce

1. Have storyshots-puppeteer setup to work with a running storybook server (not static files)
2. Make a test case fail on purpose
3. Check your storybook server console

Expected behavior
Nothing should have happened, I didn't do any code changes

Possible workaround?
Is there any way of preventing a watch on this directory?

[stale]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[stale]

Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook!