fix: add getScriptNameOrSourceURL to CallSite prototype
#865
Conversation
This file contains 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
bartlomieju
approved these changes
Aug 6, 2024
lucacasonato
approved these changes
Aug 6, 2024
marvinhagemeister
force-pushed
the
callsite-script-url
branch
from
716da7a
to
aa37057
Compare
marvinhagemeister
changed the title
getScriptNameOrSourceURL to Error prototypegetScriptNameOrSourceURL to CallSite prototype
|
Oops good point. Updated the commit message and PR here to refer to the |
devsnek
approved these changes
Aug 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Both Chrome and Node have a
getScriptNameOrSourceUrl()method on theCallSiteprototype. We didn't have that which causes an error invitest, see denoland/deno#24898