| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Could you add an entry in deprecations.md? |
Sorry, something went wrong.
|
@aduh95 not technically deprecated since not technically documented 😅 I am happy to add it to deprecations.md though this isn't going through the regular cycle. |
Sorry, something went wrong.
There was a problem hiding this comment.
I don't like naming "the next major release". I prefer if we say it is deprecated and will be removed in a future major release.
Sorry, something went wrong.
There was a problem hiding this comment.
Good idea, done
Sorry, something went wrong.
There was a problem hiding this comment.
@mcollina any chance this can get a second review? I'd prefer to make sure the changes are what you had in mind
Sorry, something went wrong.
There was a problem hiding this comment.
@mcollina ping (I'll also update it with Trott's suggestions before landing)
Sorry, something went wrong.
There was a problem hiding this comment.
Optional/non-blocking nit:
| crash the Node.js process by default. | |
| terminate the Node.js process by default. |
Sorry, something went wrong.
There was a problem hiding this comment.
| type events like `EventEmitter` does in order to be spec compliant. | |
| type events like `EventEmitter` does to be spec compliant. |
...or even:
| type events like `EventEmitter` does in order to be spec compliant. | |
| type events like `EventEmitter` does. |
It's not clear without additional context which is being spec compliant. Is it EventTarget being spec compliant but not implementing it? Or is it EventEmitter being spec compliant by implementing it? (I know the answer, or at least I think I do, but a reader may not.) Then again, maybe it's not even relevant, hence the removal suggestion above.
Sorry, something went wrong.
There was a problem hiding this comment.
We use US spellings, so this:
| be aligned with the new behaviour. | |
| be aligned with the new behavior. |
Sorry, something went wrong.
There was a problem hiding this comment.
| before reaching `process.on('uncaughtException')` - this behaviour is | |
| before reaching `process.on('uncaughtException')`. This behavior is |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM with US spelling applied to behaviour/behavior. Other changes are optional/non-blocking.
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Refs: #37237 (comment)
Refs: #37237
Basically - the "error" event is being removed from the code - it was never documented on process but in order to be cautious the change is still semver-major.
This PR changes the wording to indicate the future behaviour.
Bikeshedding/suggestions welcome