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

BrowserSync.reload call in jshint command always returns 0 file changed #593

Closed
rdmurphy opened this issue Jan 11, 2015 · 3 comments · May be fixed by tobybellwood/govstrap#4
Closed

BrowserSync.reload call in jshint command always returns 0 file changed #593

rdmurphy opened this issue Jan 11, 2015 · 3 comments · May be fixed by tobybellwood/govstrap#4

Comments

@rdmurphy
Copy link

Hello!

This line in the gulpfile.js appears to be trying to pass along to BrowserSync the number and names of the files being linted, but it always returns 0 file changed ().

screen shot 2015-01-11 at 11 09 55 am

I actually came across this with a version of the starter kit I customized to add a scripts call for concatenation + uglifying and it does the same thing there. And then I noticed it was happening twice, so I kept going up the chain and found this.

Totally possible this is on the BrowserSync side of things – not really knowledgeable enough about it to hack around on it to figure it out – but currently that is not providing any useful logged information. Could be an order of operations thing?

Hope that helps!

@rdmurphy rdmurphy changed the title BrowserSync.reload call in jshint command always returns 0 files changed BrowserSync.reload call in jshint command always returns 0 file changed Jan 11, 2015
christianvuerings added a commit to christianvuerings/browser-sync that referenced this issue Feb 11, 2015
@stevemao
Copy link
Contributor

Looks like this issue is solved.

@rdmurphy
Copy link
Author

Thanks! 👍

@addyosmani
Copy link
Contributor

Closing as fixed.

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

Successfully merging a pull request may close this issue.

3 participants