Fixes issue with multiple browser sync instances #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
HI, I noticed an issue with BrowserSync upon changes to files. I would receive an error indicating a potential memory leak with multiple instances of browserSync being unecessarily created. Below is the error message I was receiving:
This PR just simply modifies the gulpfile a bit by only calling reload and not starting a new browserSync instance on changes of files.