Import tsconfig.json in configuration without resolveJsonModule option enabled

[carlocorradini]

I have my jest configuration with .ts extension: jest.config.ts.
I'm using pathsToModuleNameMapper function to transform the TypeScript paths during testing, and I'm importing my tsconfig with import tsconfig from "./tsconfig.json".
My main tsconfig.json does not have resolveJsonModule enabled. Therefore, when calling jest it fails: Cannot find module './tsconfig.json'. Consider using '--resolveJsonModule' to import module with '.json' extension.
How can I use jest with my tsconfig without explicitly enabling resolveJsonModule in my main tsconfig? Or, in other words, can I pass resolveJsonModule: true when calling jest?
Thanks! 

[st3h3n]

For anyone who stumbles over this, here is a workaround:

import ts from "typescript";
const { config } = ts.readConfigFile("./tsconfig.json", ts.sys.readFile);
pathsToModuleNameMapper(config.compilerOptions.paths);