-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
chore: ensure AbortController installed globally #4391
Conversation
|
@@ -35,6 +36,8 @@ declare global { | |||
|
|||
ReadableStream: typeof ReadableStream; | |||
WritableStream: typeof WritableStream; | |||
|
|||
AbortController: typeof AbortController; |
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.
@jacob-ebey Looking at the abort-controller
repo, it looks like there may be a few issues with its typings that could potentially cause issues when passing signals.
mysticatea/abort-controller#16 (comment)
mysticatea/abort-controller#36
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.
It's not an issue at runtime as we are currently running tests using it. As long as the build passes and doesn't have type issues it's not an issue.
🤖 Hello there, We just published version Thanks! |
Make sure AbortController is installed globally for node version less than 15.
Closes: #
Testing Strategy:
Existing deployment tests will validate the change.