@wmonk using esnext seems to have an impact on tests (SyntaxError: Unexpected token import).
The weird part is that tests (yarn test) work on my projects created with create react app ts + changing module to esnext.
I'm not sure it's a good idea to override the tsconfig file used by jest...

@wmonk only a temporary fix (for jest) becauseTS_CONFIG is deprecated
https://github.com/kulshekhar/ts-jest
as we provide a tsConfigFile value, the module is not overwritten to commonjs...

What about creating atsconfig.test.json which uses theextends directive and overrides the module field along with the regulartsconfig.json, and update the reference totsConfigFile accordingly? Path may be added like the current one that references the regulartsconfig.json.

I.e.:
tsconfig.test.json

{"extends":"./tsconfig.json","compilerOptions": {"module":"commonjs"  }}

Add corresponding path entries inthis file, e.g.appTsTestConfig (keep in mind that there are multiple positions to be extended, i.e.L84 andL114.
As a last step, change the variablehere to your new one.

It's a bit tricky, but differentmodule values are required under different circumstances:

• esnext for the dynamic import call
• commonjs to get things working on node.js

Using different config files for both situations should be the way to go here.

Thanks!