Looks to be broken on latest Node.js (10.1.0)

[antongolub]

npm test
response › proto › on
TypeError: Cannot read property 'content-type' of undefined

Should be related to the latest http module changes: nodejs/node#20250

[apapirovski]

@antongolub Do you happen to know what's breaking it? We certainly didn't intend to break any third-party modules with that change. If you can point me to the relevant code in this module, I would be happy to look at what we can do.

Edit: Oh, I'm guessing this might be due to the some of the stricter checks. I see that you're just using prototype methods but not necessarily applying them to data matching our classes. (Our values are always null when empty but in your case it looks it's undefined.)

[antongolub]

I've used mixins and some part of OutgoingMessage constructor logic was skipped.
In my case this[outHeadersKey] equals undefined, but your commit brought more strict assertion === null. Nevermind, it's easy to fix.

And thank you for attention.

[antongolub]

🎉 This issue has been resolved in version 1.4.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀