Update internal util isError with new Error.isError #57961

Activity

1. ljharb commented on Apr 21, 2025

   

   ljharb

   on Apr 21, 2025

   SponsorMember

   More actions

   We should probably deprecate util.types.isNativeError as well as of v24?

   👍React with 👍1Reacted by Miguel Marcondes Filho

   👀React with 👀1Reacted by Miguel Marcondes Filho
2. marco-ippolito commented on Apr 22, 2025

   

   marco-ippolito

   on Apr 22, 2025

   Last edited by marco-ippolito

   Member

   More actions

   I remember deprecating all the all the util.is functions.
   util.isError is in fact EOL
   https://nodejs.org/api/deprecations.html#DEP0048
   If its not used anywhere in the codebase it can be removed

   👀React with 👀3Reacted by Jordan Harband, Jurj Andrei George and Miguel Marcondes Filho
3. miguelmarcondesf commented on Apr 22, 2025

   

   miguelmarcondesf

   on Apr 22, 2025

   Last edited by miguelmarcondesf

   ContributorAuthor

   More actions

   I remember deprecating all the all the util.is functions. util.isError is in fact EOL https://nodejs.org/api/deprecations.html#DEP0048 If its not used anywhere in the codebase it can be removed

   You're right about that, but this one is related to isError from the internal helper.
4. Renegade334 commented on May 2, 2025

   

   Renegade334

   on May 2, 2025

   Last edited by Renegade334

   Member

   More actions

   We should probably deprecate util.types.isNativeError as well as of v24?

   FWIW, I'm seeing a 50% performance regression for Error.isError over the current util/types IsNativeError binding in the latest build.
5. github-actions commented on Apr 20, 2026

   

   github-actionsBot

   on Apr 20, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been marked as stale due to 210 days of inactivity.
   It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
6. github-actions

   added

   staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.

   on Apr 20, 2026
7. github-actions commented on May 20, 2026

   

   github-actionsBot

   on May 20, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
   If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
8. github-actions

   closed this as not plannedon May 20, 2026