This patch will allow path mapping to be fully supported, by allowing moduleNameMapper to be configured.

Issue

Currently, you can add paths to your tsconfig and the app will run fine. But jest / ts-jest does not use the configuration from your tsconfig. Configuring the moduleNameMapper will solve this. Sadly, the property is not "supported" and tests can not be run if the configuration is set.

Example usage:

Changing the following files will allow you to import modules from the src folder, by prefixing the import path with a tilde. E.g. a component living in src/components/Button can always be imported via ~/components/Button. No ../../../ anymore!

tsconfig.json

{
  "compilerOptions": {
     ...
+    "baseUrl": ".",
+    "paths": {
+      "~/*": ["src/*"]
+    }
  },

package.json

{
  ...
  "jest": {
    ...
+    "moduleNameMapper": {
+      "^~/(.*)$": "<rootDir>/src/$1"
+    }
  },
}

Changes:

1. Add baseUrl so tsconfig-paths-webpack-plugin will not warn that it is missing (Fixed problem with tsconfig.json baseUrl and paths #223)
2. Allow overriding moduleNameMapper (Support for TypeScripts 'paths' option #203)

Allow overriding the moduleNameMapper configuration is the pragmatic approach. If you're using absolute paths + react-native you would have to re-add the mapping.