jest 'setupFiles' with <rootDir> breaks libs/apps tests

Prerequisites

• I am running the latest version
• I checked the documentation (nx.dev) and found no answer
• I checked to make sure that this issue has not already been filed
• I’m reporting the issue to the correct repository (not related to React, Angular or any dependency)

Expected Behavior

Properly resolve rootDir when setupFiles are being used for jest config

Current Behavior

Let’s say my root jest.config.js is using setupFiles for various reasons like

const rootConfig = {
  rootDir: '.',
  setupFiles: ['<rootDir>/test/jest/global.js']
}

now if we wanna run test for particular package which uses root as a preset, setupFiles are not found as jest sets root dir to that particular directory from where are those test executed (so instead of having root ../.. - workspace root, it’s ./libs/my-lib

Failure Information (for bugs)

● Validation Error:

  Module <rootDir>/test/jest/global.js in the setupFiles option was not found.
         <rootDir> is: /Users/hotell/Projects/devel/workspace/tools

[wilsonparson]

Just discovered Nx’s Jest builder options: https://nx.dev/web/api/jest/builders/jest#jest

Adding the setupFile property to the project angular.json seems like the best solution for our use case:

"test": {
  "builder": "@nrwl/jest:jest",
  "options": {
    "jestConfig": "libs/components-library/payment-calculator/jest.config.js",
    "tsConfig": "libs/components-library/payment-calculator/tsconfig.spec.json",
    "setupFile": "jest.setup.angular.ts"
 }
}

We’re still stuck with referencing the setup file in each individual project, but at least it’s all in one file (angular.json) instead of spread across all of our project-level Jest configs.

[vsavkin]

Sorry. The issue was marked by mistake. I removed the label.