v10.1.0

[cspotcode]

Discussion thread for the v10.1.0 release.

Release notes

[karlhorky]

@cspotcode just trying this out with the code below from jestjs/jest#11453 (comment) :

tsconfig.json

{
  "ts-node": {
    "moduleTypes": {
      "jest.config.ts": "cjs"
    }
  },
  "compilerOptions": {
    "module": "es2020",
    "target": "es2020"
  }
}

jest.config.ts

import type { Config } from '@jest/types';

const config: Config.InitialOptions = {
  moduleFileExtensions: ['ts', 'tsx', 'js'],
  moduleNameMapper: {
    '^(.*)\\.js$': '$1',
  },
  testEnvironment: 'jest-environment-node',
  transformIgnorePatterns: [
    'node_modules/(?!aggregate-error|clean-stack|escape-string-regexp|indent-string|p-map)',
  ],
};

export default config;

...and it seems like for some reason I don't need the moduleTypes configuration at all... 🤔 With ts-node@10.1.0, I needed no change to my tsconfig.json configuration below or my jest.config.ts.

Is this expected? 🤔

tsconfig.json

{
  "compilerOptions": {
    "target": "es2020",
    "lib": [
      "es2019",
      "DOM",
      "es2020.promise",
      "es2020.bigint",
      "es2020.string",
      "ESNext.String"
    ],
    "strict": true,
    "noEmit": true,
    "jsx": "react",
    "esModuleInterop": true,
    "downlevelIteration": true,
    "resolveJsonModule": true,
    "noImplicitAny": true,
    "allowJs": true,
    "checkJs": true,
    "skipLibCheck": true,
    "allowSyntheticDefaultImports": true,
    "forceConsistentCasingInFileNames": true,
    "module": "esnext",
    "moduleResolution": "node",
    "isolatedModules": true
  }
}

[karlhorky]

Ah, I think there was something wrong with the version that I had, now that I upgraded, I needed to specify this configuration in the tsconfig.json:

{
  "ts-node": {
    "moduleTypes": {
      "jest.config.ts": "cjs"
    }
  }
}