Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

moduleNameMapper doesn't handle multiple paths

See original GitHub issue

Issue :

I’m having trouble configuring jest to resolve modules when using multiple paths in my tsconfig. It seems ts-jest will only resolve a single path- is this the case?

Expected behavior :

I would expect to find some solution to resolve paths when my tsconfig.json paths array has more than one path listed. After all, it is an array ¯_(ツ)_/¯

File structure is as follows

.
├── tsconfig.json
├── jest.config.js
├── src-common
|   └── components
|       └── Button.tsx
├── src-admin
|   └── components
|       └── Login.tsx
└── src-main
    └── components
        └── Share.tsx

relevant parts of `tsconfig.json`

{
  "baseUrl": ".",
  "paths": {
    "@components/*": ["src-common/components/ui/*", "src-admin/components/ui/*", "src-main/components/*],
  }
}

`jest.config.js`

module.exports = {
  setupFilesAfterEnv: ["react-testing-library/cleanup-after-each"],
  transform: {
    "^.+\\.tsx?$": "ts-jest",
  },
  testRegex: "(/__tests__/.*|(\\.|/)(test|spec))\\.tsx?$",
  moduleFileExtensions: ["ts", "tsx", "js", "jsx", "json", "node"],
  moduleNameMapper: {
    // Resolves a single path as expected 👍 
    "^@components/(.*)$": "<rootDir>/src-common/components/$1",

    // No regex in path 😢 
    "^@components/(.*)$": "<rootDir>/src-{common,admin,main}/components/$1",

    // No array in path 😢
    "^@components/(.*)$": [
      "<rootDir>/src-common/components/$1"
      "<rootDir>/src-admin/components/$1"
      "<rootDir>/src-main/components/$1"
    ],
  },
};

Debug log:

log file content

# content of ts-jest.log :
# Project is more complex than this example, and the output doesn't exactly match ☝️

Minimal repo :

Unfortunately Codesandbox doesn’t support tsconfig.json paths 😦

Issue Analytics

State:
Created 4 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

kulshekharcommented, May 27, 2020

I think those who’ll start using jest now will start with the latest version and those who are already on v25.x, will likely have a setup that will keep working.

It might make sense to start with doing this only for 26.x for now and if there are requests for this feature in 25.x, we add it there. What do you think?

0reactions

ahnpnlcommented, May 27, 2020

Sound good to me 👍