Nx does not recognize existing jest.preset files if using .cjs or .mjs

[kevintyj]

Current Behavior

Using NX within an ESM based project, renaming jest.preset.js to jest.preset.cjs to add support for the jest preset file in cjs form.
Every time a NX generate command is ran ie: @nx/angular:library, nx does not recognize the existing jest.preset.cjs file and generates a new jest.preset.js file.
With every library creation, the generated jest.preset.js has to be deleted from project root and have to modify the generated jest.config.ts file within the new library with the correct preset path to jest preset

Expected Behavior

Recognize all accepted jest.preset file extensions jest-preset.json, jest-preset.js, jest-preset.cjs or jest-preset.mjs (https://jestjs.io/docs/configuration) from project root.

GitHub Repo

No response

Steps to Reproduce

1. Create a new NX angular monorepo
2. Change the name of jest.preset.js to jest.preset.cjs
3. Generate a new angular library using NX

Nx Report

   Node   : 21.1.0
   OS     : darwin-arm64
   pnpm   : 8.9.2

   nx (global)        : 17.1.2
   nx                 : 17.1.3
   @nx/js             : 17.1.3
   @nx/jest           : 17.1.3
   @nx/eslint         : 17.1.3
   @nx/workspace      : 17.1.3
   @nx/angular        : 17.1.3
   @nx/devkit         : 17.1.3
   @nx/esbuild        : 17.1.3
   @nx/eslint-plugin  : 17.1.3
   @nx/express        : 17.1.3
   @nx/node           : 17.1.3
   @nx/playwright     : 17.1.3
   typescript         : 5.2.2

Failure Logs

No response

Package Manager Version

pnpm 8.9.2

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

Tried editing the jest config file as shown below to see if NX recognizes the changed file. The config file has no effect on nx generate behavior and the issue is still reproduced.

import { getJestProjects } from '@nx/jest';

export default {
    projects: [
        ...getJestProjects(),
        '<rootDir>/jest.preset.cjs',
    ],
};

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.