Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(misc): override customConditions when using an incompatible module resolution #30477

Merged
merged 1 commit into from
Mar 25, 2025

Conversation

leosvelperez
Copy link
Member

@leosvelperez leosvelperez commented Mar 24, 2025

Current Behavior

In a few different places (Crystal plugins, executors, generators, helpers) where ts-node compiler options are overridden and moduleResolution is being set to something other than node16, nodenext, or bundler, an error can occur if the customConditions compiler option is being used.

Expected Behavior

When overriding the ts-node compiler options and changing forcing moduleResolution to have a value that's incompatible with customConditions, the latter should be unset (set to null) to avoid errors.

Related Issue(s)

Fixes #

@leosvelperez leosvelperez self-assigned this Mar 24, 2025
Copy link

vercel bot commented Mar 24, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Updated (UTC)
nx-dev ⬜️ Ignored (Inspect) Visit Preview Mar 24, 2025 0:54am

Copy link

nx-cloud bot commented Mar 24, 2025

View your CI Pipeline Execution ↗ for commit 450a9c9.

Command Status Duration Result
nx affected --targets=lint,test,build,e2e,e2e-c... ✅ Succeeded 35m 36s View ↗
nx run-many -t check-imports check-commit check... ✅ Succeeded 15s View ↗
nx-cloud record -- nx-cloud conformance:check ✅ Succeeded 2s View ↗
nx-cloud record -- nx format:check --base=cfe32... ✅ Succeeded 2s View ↗
nx-cloud record -- nx sync:check ✅ Succeeded 1s View ↗
nx documentation ✅ Succeeded 46s View ↗

☁️ Nx Cloud last updated this comment at 2025-03-24 13:35:16 UTC

@leosvelperez leosvelperez marked this pull request as ready for review March 24, 2025 13:09
@leosvelperez leosvelperez requested review from a team as code owners March 24, 2025 13:09
@FrozenPandaz FrozenPandaz merged commit 5dbe040 into master Mar 25, 2025
12 checks passed
@FrozenPandaz FrozenPandaz deleted the misc/fix-ts-node-overrides branch March 25, 2025 11:51
FrozenPandaz pushed a commit that referenced this pull request Mar 25, 2025
…ule resolution (#30477)

## Current Behavior

In a few different places (Crystal plugins, executors, generators,
helpers) where `ts-node` compiler options are overridden and
`moduleResolution` is being set to something other than `node16`,
`nodenext`, or `bundler`, an error can occur if the `customConditions`
compiler option is being used.

## Expected Behavior

When overriding the `ts-node` compiler options and changing forcing
`moduleResolution` to have a value that's incompatible with
`customConditions`, the latter should be unset (set to `null`) to avoid
errors.

## Related Issue(s)

Fixes #

(cherry picked from commit 5dbe040)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants