question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

BS becomes unresponsive after two file changes on Node 11

See original GitHub issue

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

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:6
  • Comments:10 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
keithwscommented, Nov 6, 2018

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.

1reaction
joemallercommented, Oct 31, 2018

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

node.js - 'node' is not recognized as an internal or an external ...
1) open Control Panel -> System and Security -> System -> Advanced System Settings -> Environment Variables · 2) in "User variables" or...
Read more >
You should never ever run directly against Node.js in ...
The development problem is that when we change the code, we have to stop and start the application to get our changes picked...
Read more >
6 reasons your Node.js apps are failing - IBM Developer
2. Excessive memory usage, which may result in an out-of-memory error. Excessive memory usage by a Node application is often detected by scripts...
Read more >
A simple guide to JavaScript concurrency in Node.js | TSH.io
In the article about JavaScript concurrency in Node.js, the author clarifies how Node deals with asynchronicity. What are the biggest traps?
Read more >
node/CHANGELOG_V14.md at main · nodejs/node - GitHub
This update is not being treated as a security release as the issues addressed in OpenSSL 1.1.1o were assessed to not affect Node.js...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found