Add patchStackTrace export; test that all named exports are detected by Node
#5411
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
|
Thanks! |
STRd6
approved these changes
Apr 19, 2022
GeoffreyBooth
force-pushed
the
add-patch-stack-trace-export
branch
from
f1f74ad to
0c187d6
Compare
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.
Follow-up to #5403; this adds the new
patchStackTraceexport, so thatimport { patchStackTrace } from 'coffeescript'works in Node’s native ESM. I noticed this while writing up the changelog.I also added a test so that we don’t miss these in the future. cc @STRd6