-
Notifications
You must be signed in to change notification settings - Fork 754
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 Proxy & Reloading #1327
Comments
What do you mean by 'it never gives me a confirmation after the fact' - what's your expectation? |
Well, when you use |
Ahh I see. Well there's no concept (atm) of browsers validating a message was received I'm afraid |
I understand that this might seem trivial, it's just annoying when you're bug hunting a build process and you're not sure where the issue is and if the messages leaves you hanging on like that, it could point you in the wrong direction. |
@camdagr8 If you turn Also, if you have the network tab open of any dev tools you should see a reload happen. Not going to help you if you're using the CLI to see when it's been reloaded, but maybe that would be sufficient. |
Issue details
I'm using BrowserSync via gulp with a node server running so I'm proxying to that. Then I'm using nodemon (https://www.npmjs.com/package/gulp-nodemon) to watch for changes on my server. When changes are made, the browserSync.reload() function is called.
When the reload is triggered I get:
[14:05:02] [nodemon] restarting due to changes... [14:05:02] [nodemon] starting `node ./dist/index.js` [14:05:04] [NODE] Server running on port: 9000 [BROWSERSYNC] Reloading Browsers...
The reload actually happens but it never gives me a confirmation after the fact. It's been annoying the crap out of me as I can't figure out why.
Affected platforms
Browsersync use-case
The text was updated successfully, but these errors were encountered: