-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
Make DOMException globally available #39098
Labels
feature request
Issues that request new features to be added to Node.js.
Comments
himself65
added
the
feature request
Issues that request new features to be added to Node.js.
label
Jun 21, 2021
If nessesary, I will do this after #39105 is landed. |
XadillaX
added a commit
to XadillaX/node
that referenced
this issue
Jun 28, 2021
XadillaX
added a commit
to XadillaX/node
that referenced
this issue
Jun 28, 2021
XadillaX
added a commit
to XadillaX/node
that referenced
this issue
Jun 28, 2021
XadillaX
added a commit
to XadillaX/node
that referenced
this issue
Jun 28, 2021
XadillaX
added a commit
to XadillaX/node
that referenced
this issue
Jun 30, 2021
XadillaX
added a commit
to XadillaX/node
that referenced
this issue
Jun 30, 2021
XadillaX
added a commit
to XadillaX/node
that referenced
this issue
Jun 30, 2021
XadillaX
added a commit
to XadillaX/node
that referenced
this issue
Jun 30, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Having to do this is bad code smell
Since we are aligning more with Web standard APIs now days with the arise of URL, URLSearchParams, Event & EventTarget, MessageChannel, Workers, BroadcastChannel, Blob, File, AbortController, atob, bota, TextEncoder, TextDecoder etc
It would only start to make sense to expose DOMException globally so you are able to check if a error is a instances of DOMException.
Pollyfills need this Error class also.
And more feature web standard apis is probably going to need it.
The text was updated successfully, but these errors were encountered: