Skip to content
This repository has been archived by the owner on Jan 11, 2019. It is now read-only.

Timed out waiting for dist/*.js after 30 seconds #126

Closed
chuntley opened this issue May 25, 2016 · 2 comments
Closed

Timed out waiting for dist/*.js after 30 seconds #126

chuntley opened this issue May 25, 2016 · 2 comments

Comments

@chuntley
Copy link

chuntley commented May 25, 2016

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?

@neilkyoung
Copy link

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.

@johneisenheim
Copy link

Hi there!
I experienced the same problem! In my case, I solved increasing the just-wait time in package.json.

"watch-server-start": "node node_modules/just-wait -t 50000 --pattern \"dist/*.js\" && npm run start".

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants