fix(js): babel preset should also check for JEST_WORKER_ID to transpile to CJS #21754
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.
This PR fixes a longstanding issue with
@nx/js/babel
whereNODE_ENV
being anything other thantest
will cause errors due to modules being transpiled as ESM (and Jest not able to run it).Previously, our
@nx/jest:jest
executor guarantees thisNODE_ENV
istest
, but now with Project Crystal we are skipping the executor. To know whether we're in Jest context, we should check theJEST_WORKER_ID
which is always set when using Jest runner.For example, if you generate an app and run Jest with
NODE_ENV
set to anything else you'll see an error.Current Behavior
Setting
NODE_ENV
to anything other thantest
will result in test failure.Expected Behavior
Our test setup should be resilient against
NODE_ENV
not beingtest
.Related Issue(s)
Fixes #