-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: AbortError
#1744
feat: AbortError
#1744
Conversation
@node-fetch/core Is updating v2 like this still a thing we can and should do? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see a reason not to. As long as it's not a breaking change
Following up on my open PRs, any plans to merge this? If not, I can close this. |
as there was no objection, I'm going to merge it in 👍🏼 Sorry for the delay |
🎉 This PR is included in version 2.7.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Purpose
Backport of 553bb5d to v2.
Changes
Exports the AbortError, which is used internally and thrown on a timeout. https://github.com/node-fetch/node-fetch/blob/2.x/src/index.js#L81
Additional information
#792
AbortError
is not exported #792