BS becomes unresponsive after two file changes on Node 11

[DimitarNestorov]

Issue details

It seems that there is some kind of endless loop triggered after a couple of file changes.

Here's a video showing off the issue: https://youtu.be/MfnATcrsXt0
It's quite long, here are some timestamps:
00:00 - I run Browser Sync
02:30 - I create test.js
02:39 - I change test.js
03:16 - I change test.js again
03:24 - Browser Sync becomes unresponsive

I tested latest Node 10, the issue doesn't occur there.

Steps to reproduce/test case

1. Clone https://github.com/dimitarnestorov/browsersync-node11.git
2. Install dependencies
3. Run node script.js
4. Create a random file inside the build folder
5. Make a change inside the new file
6. Make another change inside the new file

Please specify which version of Browsersync, node and npm you're running

• Browsersync [ 2.26.3 ]
• Node [ 11.0.0 ]
• Npm [ 6.4.1 ]

Affected platforms

• linux
• windows
• OS X
• freebsd
• solaris
• other (please specify which)

Browsersync use-case

• API
• Gulp
• Grunt
• CLI

[rawzone]

Also seeing this when using browsersync with laravel-mix running under Linux.

• Browsersync [2.26.3]
• Node [11.0.0]
• Yarn [1.10.1] [1.12.1]

Same behavior as on the YouTube video @DimitarNestorov posted how ever the number of times before it stops responding varies for me for each time i relaunch browsersync.

Have tried to disable all ipv6 networking to ensure it was not a problem resolving localhost / 127.0.0.1 but does not seem to have made any difference.

Edit: Just upgraded Yarn to latest version, this didn't change anything.

[joemaller]

I think I'm seeing the same thing. No luck downgrading browsersync, but after switching node down to v10.x (and rebuilding node_modules) browsersync has been working smoothly for a couple hours.

[JuanDMeGon]

Facing the same with Node 11.0.0 on Windows 10 x64.
Just in case. I am using Laravel mix as well (which uses webpack) and Browser-sync ^2.26.3 along to browser-sync-webpack-plugin ^2.2.2.
After removing NPM 11.0.0 and install Node 10.13.0LTS, then remove node_modules and package-lock.json (just in case) it works as expected again.

[WuglyakBolgoink]

same :(

[keithws]

Same issue here but I am not using Laravel nor weback. I have it configured to watch a few thousand static files. Works fine on Node 10.x. Locks up after a few minutes on Node 11.x. Browser-sync 2.26.3.

[WuglyakBolgoink]

FYI: yesterday I upgraded my NodeJS version with v11.1.0 -> BS working again as before. 👍

Please test this.

[waltercruz]

Yes, node 11.1 solved the issue to me.

[roberthallatt]

Also solved it for me

[rawzone]

Also confirmed fixed after upgrading node to v11.1.0.

[jmcbee]

I thought I was going crazy. Thank you!