fix(no-deprecated-api): dedeprecate process.nextTick
#350
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Matteo Collina <hello@matteocollina.com>
MichaelDeBoey
changed the title
process.nextTick
|
This was a misunderstanding on my part, Sorry! Thank you for the PR |
MichaelDeBoey
approved these changes
Oct 9, 2024
scagood
approved these changes
Oct 9, 2024
|
The PR at fault #342, the specific commit: |
This was referenced Nov 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've recently noticed that this module is starting to tag
process.nextTick()as deprecated. But it's not. Essentially it's close to impossible to stop using for old code, because it will alter the order of callbacks being fired.Here is the full discussion: nodejs/node#51280. Note that Node.js still uses it everywhere, because it's not possible to replace it without breaking a lot of people.