Repository navigation
http: OutgoingMessage streamlike #28969
Description
http OutgoingMessage is missing some methods, properties and behaviours to make it "truly" "streamlike":
-
destroyed -
writableLength(http: OutgoingMessage stream properties #29018) -
writableHighWaterMark(http: OutgoingMessage stream properties #29018) -
writableCorked -
writableObjectMode(http: OutgoingMessage stream properties #29018) -
cork()(http: outgoing cork #29053) -
uncork()(http: outgoing cork #29053) -
ERR_STREAM_DESTROYED(http: align with stream.Writable #31818) -
instanceof Writable(issue http: OutgoingMessage instanceof Writable #28971)
Furthermore the destroy event ordering does not seem to be fully consistent with the stream implementation (needs further investigation).
Activity
[-]http: outgoing missing properties[/-][+]http: OutgoingMessage as Writable[/+][-]http: OutgoingMessage as Writable[/-][+]http: OutgoingMessage streamlike[/+]mcollina commentedon Aug 5, 2019
Great initiative, definitely +1 to add all of these!
awwright commentedon Jul 5, 2020
Is there some reason that OutgoingMessage is not an ancestor of Writable?
ronag commentedon Jul 5, 2020
Performance
bjohansebas commentedon May 24, 2025
Is there any actionable item?
github-actions commentedon May 24, 2025
This issue/PR was marked as stalled, it will be automatically closed in 30 days. If it should remain open, please leave a comment explaining why it should remain open.
github-actions commentedon Jun 24, 2025
Closing this because it has stalled. Feel free to reopen if this issue/PR is still relevant, or to ping the collaborator who labelled it stalled if you have any questions.