Output any kind of debug info to the output

[markelog]

Did the installation path, added one withScreenshot() for testing to a relatively big size (I think) storybook.

After the
$ ./node_modules/.bin/storybook-chrome-screenshot -p 9001 -c .storybook

I get

 LAUNCH  Launching storybook server ...
 PREPARE  Fetching the target components ...

And nothing else.

localhost:9001 shows me the storybook normal build version, no errors, shows element with withScreenshot as well.

Would want to debug it, but it seems futile without any kind of logs, the suggestions or something from the tool would be helpful

[markelog]

After 20 minutes it unfrozed, yey! But issues still stands though.

Also it seems performing significantly slower then @storybook/addons-storyshots (newer version can do screenshots). With the difference that they already performing the image comparison which should be one of the slowest parts? And I only did one test screenshot, whereas addons-storyshots did all of them.

Have you considered any performance improvements, it's a bit off-topic but still? Should I create an issue about it?

[wadackel]

Hi @markelog, Thank you for Issues 😃

I'm also aware of performance problems... 😇
However, we are still struggling to improve now.

By the way, when debugging, use the --debug flag to get the output.

[wadackel]

By PR #50, the performance of CAPTURE phase has improved 👍
Performance improvement will be done little by little in the future.

---

I think that the content of the title has been solved, so may I close this Issue 😃 ??

[markelog]

Sounds good, looking forward to testing it :)