-
Notifications
You must be signed in to change notification settings - Fork 60
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
livereload does not seem to work with watch #53
Comments
I made a minimal example, and it doesn't reload, either:
It starts & stops the server, but no live-reload in chrome. |
hhhhwhat!?!?! I'll test this out & get this crap fixed. @ericclemmons probably screwed up :) |
Hehe. no biggie. I been meaning to try out gulp, but may be good for yeomanites. Is there some client-side magic js that needs to be injected or something? |
I think you simply forgot to specify livereload: true for watch
|
I have a similar issue. Livereload refreshes the browser before express has a chance to start.
|
I took a look at your issue on spawning a coffee child process doesn't work as expected and repeated your test of test.coffee:
subtest.coffee:
and got matching pid everytime
Should this allow the server to be restartable, if the coffee process can be killed? |
hmm .. then it should work. Could you provide more information, to make it reproducible? |
Package.json
Gruntfile.js
app.js
This doesn't reload properly. It seems livereload refreshes the page before the server can start. Although even adding a delay doesn't help so something else might be going wrong.
|
Ok. I could reproduce and workaround .. but I'm not understanding why. doesn't work
works
could also be a problem of grunt-contrib-watch |
Weird.. the workaround doesn't work for me. Same issue. |
yeah .. doesn't work for me anymore, too. |
ok .. I found the bug in here |
Awesome, thanks for the help! |
Livereload refreshes the browser before express has a chance to start. |
This should be resolved via |
I am using yeoman. I want to replace grunt-contrib-connect with this module, so I can run my express server. I probably just missed something, but I can't seem to get it to work like grunt-contrib-connect does with a static dir. The relevant parts of my grunt config look like this:
My task looks like this:
The text was updated successfully, but these errors were encountered: