Replies: 4 comments 1 reply
-
Feel free to open a PR. The folders in |
Beta Was this translation helpful? Give feedback.
-
Um... I am not sure that's a good idea. I had to add all of these settings to the configuration files to make this work in the separate folder. {
moduleFileExtensions: ['js', 'mts'],
resolver: '<rootDir>/mjs-resolver.ts',
testMatch: ['**/__tests__/**/*.m[jt]s?(x)', '**/?(*.)+(spec|test).m[tj]s?(x)'],
transform: {
'^.+\\.mtsx?$': [
'ts-jest',
{
tsconfig: 'tsconfig.json',
useESM: true,
},
],
},
} So this would be a much more invasive change across all the example folders than I think you or other ts-jest maintainers would like. I do see your point about slowing down CI. Maybe this is a big code smell telling us to add support for the But hey, branches are cheap, so I'll prepare both of the first two options, and submit the second one as a pull request as you've directed. |
Beta Was this translation helpful? Give feedback.
-
Could someone please mention or describe the commitlint / (Edited because a few minutes' reflection shows I was being rude, and that is not my intention. My apologies.) |
Beta Was this translation helpful? Give feedback.
-
Pull request #3963 filed. |
Beta Was this translation helpful? Give feedback.
-
Hello. Like others, I have fiddled with trying to get TypeScript modules (
.mts
) supported. I have locally modified theexamples
directory with a working set of configurations, based on thetype-module
example. I have it in my local copy atexamples/mts-module
.I'd like to add this as a pull request, to show people "here's a working set of examples where your specs are written as TypeScript modules."
The "Contributing" guide suggests I should come here first.
Beta Was this translation helpful? Give feedback.
All reactions