fix(misc): prevent ts-node from reading tsconfig when registering transpiler #21381
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.
Current Behavior
When registering the
ts-node
transpiler, we provide the compiler options that were already read from the tsconfig file. Then,ts-node
loads again the tsconfig file to read the same compiler options already provided.Expected Behavior
When registering the
ts-node
transpiler we preventts-node
from rereading the tsconfig file. The already provided compiler options are all that's needed.Note: we should do something similar when registering the SWC transpiler (don't set the
SWC_NODE_PROJECT
env var), but there's currently an issue swc-project/swc-node#716 where provided compiler options are just plainly ignored and the config is always read. While that issue was already addressed, the fix hasn't been released yet: swc-project/swc-node#750. Even when it gets released, we probably can't rely on that unless we check which version it's installed in the workspace, because it might not contain the fix.Related Issue(s)
Fixes #