fix: sourcemaps for pirates hook. #350
Merged
Conversation
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
Contributor
Author
|
What's the plan for Node v20.x support? It reaches EOL in April. |
Member
Let's keep it until it reaches EOL |
Brooooooklyn
approved these changes
Dec 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
I was still encountering wrong stack traces as described in #161.
Effectively all files will be run through the pirates hook based on the file extensions it registers, so even though I was running
@oxc-node/core/registerfrom a project defined as"type": "module", the ESM loader never ran, and I was still getting bad line/column numbers from the CJS transform.Is
@oxc-node/core/esmexpected to be used directly?