DeprecationWarning for OutgoingMessage.prototype._headers

[rgladwell]

Accessing the HTTP server throws a DeprecationWarning for OutgoingMessage.prototype._headers on Node version 12.3.1.

const puppeteer = require('puppeteer')
const httpServer = require('http-server')
const server = httpServer.createServer({ root: 'dist/html/' })
server.listen(8080)

const browser = await puppeteer.launch({
  headless: true,
  args: ['--no-sandbox', '--disable-setuid-sandbox']
})

const page = await browser.newPage()
await page.goto('http://localhost:8080', { waitUntil: 'networkidle0' })

What did you expect to happen?

No deprecation warning.

What actually happened?

Got the following warning:

(node:59243) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated

If the issue is a feature request, what is the motivation / use case for it?

Tell us about your environment

• http-server version: 0.11.1
• Platform: Mac (Node 10.14.5 12.3.1)

[Xmader]

flatiron/union#64

[Smilebags]

The same occurs when using http-server from the command line. I wonder if this could be resolved?

[Lemraj]

I am having the same problem when running http-server (local).

I have a simple angular app:
1 - ng build --prod
2 - go to dist/{name-app}
3 - run http-server

when browsing the url i get the following error:

[thornjad]

This is an issue in union (flatiron/union#64) which we're planning to remove from http-server down the road (#483). I'm not going to close this issue though, to ensure we make sure it goes away after #483 is resolved.

[rsail]

Is there an ETA when this will be resolved?

[jmcollin78]

Always the problem with very latest build (April 2021). An estimated ETA or fix would be greatly appreciated

[Dragonrun1]

Over 2 years now. How much longer until this is fixed?

[Saqib92]

I was running another server on same port (using XAMPP server). I stopped XAMPP and restarted my cmd and its working now.

[rich1n]

Still the bug alive? or it is solved?

[thornjad]

This is an upstream bug in the dependency union, which is more or less unmaintained. #483 seeks to remove it, but it will take some substantial work. For the time being, I'm not aware of plans to imminently remove the _headers property in Node, so we're not at a crisis point yet. I may not have the time to get to #483 for a while, and would welcome any PRs.

[github-actions]

This issue has been inactive for 180 days

[spacecowgoesmoo]

Still happening

[ssaakkiii]

Can't believe it's now 2022 and the bug still exists... Orz

[Eli250]

I have met the same error

[Zwiqler94]

Any updates on this?

[mirabilos]

Might be useful to spin a new version of union fixing just this…?

[Jaystar-Bee]

This issue is still not fixed yet!!

[JobinZe]

Is there any solution for this?

[kburns2kb]

Howdy, still not fixed

[MarwenLabidi]

same problem

[omarzougui]

Same problem on Nx monorepo with node v19.7.0

[jaanus]

Another passer-by surprised by this bug. Was looking for a small Node static web server to run a static site so I can Playwright tests against it during development/CI. This project seems to fit the bill, but this warning is unfortunate.

[akadori]

same problem.

[work933k]

Same here

[eldritchT]

Same with node v18.15.0 :(

[FunctionPoint]

Still present with Node.js v21.2. Please fix..

[vitalets]

Temporary solution is to suppress Node.js warnings:

NODE_NO_WARNINGS=1 npx http-server .

[muhamedoufi]

try npm audit fix --force

[elmalving]

As the status says - the issue is still open ;-;