Ahn

Please check https://github.com/facebook/jest/issues/10550 because it relies on that. Besides, you can also look at the current codebase of `ts-jest` to see any suspicious points, here is the part using TypeScript...

Currently no unfortunately :) for `isolatedModules: true` nothing much to do for it. For `isolatedModules: false`, there might be a way.

yes `babel-jest` does support TypeScript. You just need to configure Babel to use TypeScript plugin and it will do the job. You can either use `babel-jest` to process TypeScript or...

That is possible, I’m curious how significant the improvement is when disabling source map.

@sinbargit you can now disable source map with `ts-jest` **27.0.0-next.12** and `jest` **27.0.0-next.9** by setting `sourceMap: false` in your test tsconfig.

Can you pls open a separate issue with a repo for it?

The unit test data was wrong for `MockMethods`. It is just a constant and we didn’t put any `jest.mock` which uses that constant. We copied the test data from Jest...

There is one solution I can think of is: including the variables starting with `mock` into the list of statements to sort, see this https://github.com/kulshekhar/ts-jest/blob/45a39140713cf0b72d143816609c6ffa69e0141f/src/transformers/hoist-jest.ts#L86 If we do that way,...

When you run Jest in ESM mode, it is required to use `@jest/globals` because Jest ESM mode doesn't inject global `jest` object by default.

`jest.mock` isn't supported in ESM mode yet, see https://github.com/facebook/jest/pull/10976 Also you should take a look at https://github.com/facebook/jest/issues/9430 and search for keyword `jest.(do|un)mock` I can conclude this is not an issue...