fix(core): Corrected fetch module DOMException reference#11262
Merged
CatchABus merged 1 commit intoJun 8, 2026
Merged
Conversation
|
View your CI Pipeline Execution ↗ for commit 5366f10
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
CatchABus
approved these changes
Jun 8, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
PR Checklist
What is the current behavior?
In
@nativescript/core/fetch/index.mjssignal.abortedandxhr.onabortare both still referencingexports.DOMExceptionwhich seems to be the old CommonJS pattern. From my tests, without the change any fetch / axiosCancelToken/AbortControllercancellation will triggerReferenceError: exports is not defined at xhr.onabort.What is the new behavior?
Updated
@nativescript/core/fetch/index.mjsso thatDOMExceptionis referenced correctly. Rather than usingexports.DOMExceptioncode now simply usesDOMException.Fixes/Implements/Closes #11238.