fix(js): set compilerOptions correctly when loading .ts that targets ESM #27862
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.
When we load
.ts
files and the closestpackage.json
specifies"type": "module"
, then the file may error upon loading. This happens because we're not settingcompilerOptions
correctly when registeringts-node/esm
-- in fact there is no way to pass options through this hook.This PR sets defaults on
TS_NODE_COMPILER_OPTIONS
such that themodule
andmoduleResolution
are correct values for ESM. It also works for CJS since bothmodule
andmoduleResolution
check the closestpackage.json
to determine the format.Current Behavior
Expected Behavior
Related Issue(s)
Fixes #23228