-
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
[DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated when Browsersync: Connected #1688
Comments
I have the same problem |
Hey @suhailkc I had to downgrade to node 10.15.3 LTS to solve it. |
It's just a warning, so it seems we can ignore it for now. But it'd be nice if this was fixed at some point @shakyShane :) |
I'd submit a PR, but I'm not familiar with the codebase. |
I have the same problem,what is the solution? |
You ignore the warning, or wait, or use Node.js < 12.x. |
thanks! |
for the record, the Original post implies "it stops working" but I can see things refreshing on my machine! I'm using Gulp and I'm not denying existence of your issue, I'm saying maybe something is wired up not the right way if refreshing is not happening? Either way, I hope the API will be updated soon and |
Same warning on |
Same warning using |
Use getHeaders or _headers - fixes #1688
Fixed by updating "browser-sync": "^2.26.7". |
For someone who came here for solution: |
I'm working with express v4.17.1 and node 12.13.1 and for me the problem is still present |
Same is the case for me : express v4.17.1 and node 12.13.1 . What is the solution? |
If you come here from Google, you can fix them by upgrade express to version 4.17.1 then an error has gone. |
Issue details
As soon as I connect to the server (localhost:3000) I received the following message:
(node:37943) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
Steps to reproduce/test case
Use node, npm and gulp as indicated below. All the tasks load properly, but when connected with browser-sync at localhost:3000 node sends the DEP0066 message and it stops working.
Please specify which version of Browsersync, node and npm you're running
Affected platforms
Browsersync use-case
for all other use-cases, (gulp, grunt etc), please show us exactly how you're using Browsersync
The text was updated successfully, but these errors were encountered: