You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2019. It is now read-only.
On OSX, after running npm run watch I periodically get the error:
Timed out waiting for dist/*.js after 30 seconds npm run watch-server-start exited with code null Sending SIGTERM to other processes..
The server never starts because of this, so I end up having to rerun the watch command. If I run watch, then change a couple of files, sometimes it will catch the change and run the server. Any ideas on what could be causing this?
The text was updated successfully, but these errors were encountered:
Every now and again I get issues when running npm run watch. To resolve this I normally just remove all the hot update files (*.js, *.map & *.json) in that directory and it resolves the issues.
On OSX, after running
npm run watch
I periodically get the error:Timed out waiting for dist/*.js after 30 seconds
npm run watch-server-start exited with code null
Sending SIGTERM to other processes..
The server never starts because of this, so I end up having to rerun the watch command. If I run watch, then change a couple of files, sometimes it will catch the change and run the server. Any ideas on what could be causing this?
The text was updated successfully, but these errors were encountered: