You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I debugged through my code 20 times, I swore it was this then I swore it was that, but turns out no obvious part of my code is causing the error. I am on Windows, I don't believe the problem happens on OSX, tried on both, only happens on Windows, unfortunately, it's not clear at all where it originates from.
Without some minimal reproduceable code It's very hard for anyone to guess why this occurs. But the error is thrown because you're trying to write to a socket that is closed.
If you're using a specific library, I'd personally try to isolate this, and check with library authors (because this looks like a user-land error, not node itself).
This isn't the right place for general support questions. Please move your questions to https://github.com/nodejs/help. If you discover an actual bug with Node, please report it here.
Well it appears to be a bug with Node, if only because Windows and OSX act differently with core code, it may because of fs-events from chokidar, but that's just a guess
If you think it might be a bug in Node core, please provide a runnable example that reproduces the problem without any external dependencies like fs-events.
Activity
fl0w commentedon Apr 21, 2016
Without some minimal reproduceable code It's very hard for anyone to guess why this occurs. But the error is thrown because you're trying to write to a socket that is closed.
If you're using a specific library, I'd personally try to isolate this, and check with library authors (because this looks like a user-land error, not node itself).
cjihrig commentedon Apr 21, 2016
This isn't the right place for general support questions. Please move your questions to https://github.com/nodejs/help. If you discover an actual bug with Node, please report it here.
ORESoftware commentedon Apr 21, 2016
@cjihrig np, noted thanks
ORESoftware commentedon Apr 22, 2016
Well it appears to be a bug with Node, if only because Windows and OSX act differently with core code, it may because of fs-events from chokidar, but that's just a guess
cjihrig commentedon Apr 22, 2016
If you think it might be a bug in Node core, please provide a runnable example that reproduces the problem without any external dependencies like
fs-events.