`yarn watch --filter=COMPONENT_NAME` consistently fails during local development

[jamieomaguire]

On my Macbook Pro I often notice that saving file changes to any file within a component package currently being served by yarn watch results in an error (images attached).

I have encountered this error for pretty much all of our components, and it appears to happen regardless of whether or not the file had any errors in it at the time of saving.

Storybook changes never result in this issue, so I am fairly confident it is specifically related to packages and perhaps a dependency.

Has anyone else encountered this? It means roughly every 2-3 file changes I have to restart yarn watch.

Steps to reproduce:

It seems to happen whether or not you make an actual change to the file or just save the file with no changes.

1. yarn
2. yarn dev --filter=pie-storybook
3. yarn watch --filter=pie-modal
4. make a change to index.ts and save - nothing should break
5. make another change to index.ts and save - nothing should break
6. make a change to defs.ts (or just save the file again with no changes) - error should occur

[raoufswe]

I can confirm I've been facing the same issue for a while as well. will try to gather more details.

[xander-marjoram]

I've seen this issue before but I can't say I remember seeing it recently.

A couple of things we should probably try are making sure we're using the latest versions of Storybook and are providing all the requested peer dependencies, that should get us in a good place to investigate (or hopefully it resolves it!)

I've made #779, if you could try pulling that down and trying to reproduce that would be great!

[xander-marjoram]

I managed to reproduce the issue on the branch for #779 so that won't solve it. There were lots of console errors so that's something to explore.

[xander-marjoram]

@jamieomaguire Is this something you still notice happening? I don't usually use the watch command so can't say I've noticed it recently