
Its really annoying to have to scroll to see my own logs.
Can I see your browser-sync configuration
https://gist.github.com/jgatjens/40cd97dba9bba29e74a1
node -v v0.11.13
browser-sync -v 1.3.7
Thanks,
@jgatjens - can you upgrade to 1.5.1 and report back if the issue is still there?
Basically I've never seen that output (it's from socket.io, not the BrowserSync JS) - are you using socket.io yourself?
Thanks for answering back !
I upgrade to 1.5.1 and is still there. I am not using socket.io. I used the gulp-angular generator from yeoman to scaffolding the app.
Is annoying but whatever I can live with that for now.
Hey @shakyShane,
I found that Chrome was actually the problem. I reset chrome defaults settings and the logs are gone !
Cool!
I'm getting this same same issue. @jgatjens when you say "I reset chrome defaults settings" what did you do?
Don't worry, I was able to track it back to a local storage settings called debug which was set to * for some reason.
Thanks @avanderhoorn
To be more specific for guys facing this problem in the future, type the following in the chrome dev console
localStorage["debug"] = null
I'm not sure what this value means, but setting it to null, there's no browserify annoying messages, and console.log in my app still works well.
:+1:
:+1:
:+1:
I also had this problem. It's caused by visionmedia/debug, which relies on this localStorage flag to configure logging. currently, there's no option to namespace the config, which means that there's no way to turn logging off for browsersync but keep it on for other components which use debug
Most helpful comment
Thanks @avanderhoorn
To be more specific for guys facing this problem in the future, type the following in the chrome dev console
I'm not sure what this value means, but setting it to null, there's no browserify annoying messages, and
console.login my app still works well.