fix(misc): override customConditions
when using an incompatible module resolution
#30477
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
In a few different places (Crystal plugins, executors, generators, helpers) where
ts-node
compiler options are overridden andmoduleResolution
is being set to something other thannode16
,nodenext
, orbundler
, an error can occur if thecustomConditions
compiler option is being used.Expected Behavior
When overriding the
ts-node
compiler options and changing forcingmoduleResolution
to have a value that's incompatible withcustomConditions
, the latter should be unset (set tonull
) to avoid errors.Related Issue(s)
Fixes #