Skip to content
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

Foundation 6 - Only first change in the src folder is watched #1623

Closed
grosewarne opened this issue Apr 29, 2016 · 6 comments
Closed

Foundation 6 - Only first change in the src folder is watched #1623

grosewarne opened this issue Apr 29, 2016 · 6 comments

Comments

@grosewarne
Copy link

grosewarne commented Apr 29, 2016

I am using foundation 6.2
With the lastest update
Only first change in the src folder is watched after that it stops.
It serve only first change, and ends with "Reloading Browsers..."

@alexandru-calinoiu
Copy link

I have the same issue but with a stylus compile task, when the compilation fails gulp will exit.

@phated
Copy link
Member

phated commented Apr 29, 2016

Can someone please tell them to stop suggesting using the new-docs branch? That is a terrible suggestion. I'm not going to create an account there.

@phated
Copy link
Member

phated commented Apr 29, 2016

Alright, I tracked down the first issue (haven't investigated @alexandru-calinoiu's since you clumped it together in this issue). @grosewarne the way foundation-zurb-template is using browser.reload is incorrect and the only reason it was working in the first place was some inconsistencies in gulp. With the switch to glob-watcher version 3, we have normalized the behavior and now all watch tasks are async; however, foundation-zurb-template is using a sync browser.reload call as a "task".

@phated
Copy link
Member

phated commented Apr 29, 2016

@grosewarne foundation/foundation-zurb-template#37 please inform whoever to merge that and use my fork/changes until it is merged.

@phated
Copy link
Member

phated commented Apr 29, 2016

@alexandru-calinoiu your problem doesn't exist for me when using the same changes I PRed for @grosewarne's problem. Not sure if that's what solved it or if you have something else going on.

Closing this.

@alexandru-calinoiu
Copy link

alexandru-calinoiu commented May 3, 2016

@phated not sure what the problem is just yet will investigate and open a issue if there is one related to gulp.

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

No branches or pull requests

3 participants