-
Notifications
You must be signed in to change notification settings - Fork 8
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
yarn watch --filter=COMPONENT_NAME
consistently fails during local development
#777
Comments
yarn watch --filter=COMPONENT_NAME
consistently fails during local development
I can confirm I've been facing the same issue for a while as well. will try to gather more details. |
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! |
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. |
@jamieomaguire Is this something you still notice happening? I don't usually use the |
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.
The text was updated successfully, but these errors were encountered: