| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Both of these should always refer to the same error, hence there is no reason to separate them.
|
@nodejs/streams |
Sorry, something went wrong.
| called in order to fully uncork the stream. | ||
|
|
||
| ##### `writable.writableErrored` | ||
| ##### `writable.errored` |
There was a problem hiding this comment.
needs changes: entries?
Sorry, something went wrong.
There was a problem hiding this comment.
These props have never made it to any release... is that really necessary?
Sorry, something went wrong.
| }, | ||
|
|
||
| readableErrored: { | ||
| errored: { |
There was a problem hiding this comment.
Do the readableErrored and writableErrored need to go through a deprecation cycle first? Those should likely be runtime deprecated aliases, yes?
Sorry, something went wrong.
There was a problem hiding this comment.
Not really. They haven’t been in any release.
Sorry, something went wrong.
|
I've remove the semver-major label as per #40799 (comment). |
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Both of these should always refer to the same error, hence there is no reason to separate them.
Refs: #40696