fix(node): enhance error messaging for fetchAndRun with url #3729
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.
Description
I have noticed that when
loadRemote
fails because fetching a given file is unsuccessful, the URL that was attempted to fetch is not available. See my previous PR which dealt with allowing retries to function properly.This change to the node runtime plugin will generate a new error, assigning the caught error as the
cause
. To do so, I added"lib": ["es2022.error"],
to the tsconfig for node package. Doing so caused some other ts errors which I resolved.In addition, I added some unit tests, to assert:
error.message
Example error before :
... not great... Example error after :
Related Issue
#3685
Types of changes
Checklist