-
Notifications
You must be signed in to change notification settings - Fork 31.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Closed WritableStream causes ERR_INTERNAL_ASSERTION #57272
Comments
/cc @nodejs/whatwg-stream |
This was referenced Mar 2, 2025
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Version
v22.14.0
Platform
Subsystem
Web Streams
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
When this program runs, it should print something like the following:
The correct behavior is that after the stream is closed, continuing to write will cause a
TypeError
saying that the stream is closed.What do you see instead?
Instead, the new version of Node.js v22.14.0 prints this:
Additional information
The correct behavior is consistent with Deno, Bun, the browser, and previous Node.js versions, i.e.
v22.13.1
and before, but recent versions, such asv22.14.0
, are broken.The text was updated successfully, but these errors were encountered: