When I have diagnostics: false jest still prints out type errors

🐛 Bug Report

seems to me like diagnostics: false should ensure that we only transpile without doing any type checking

To Reproduce

Steps to reproduce the behavior: run any code with a type error with

  globals: {
    'ts-jest': {
      diagnostics: false
    }
  }

in your jest.config.js

this is for my test:

Expected behavior

no type errors are checked

Link to repo (highly encouraged)

Debug log:

# content of ts-jest.log :

envinfo

System:
    OS: ubuntu 21.04
    Node version: 16

Npm packages:
    jest: 27
    ts-jest: 27
    typescript: 4.4.2
    babel(optional):

[slinkardbrandon]

I have the same issue on Mac (Big Sur: 11.5.2), I cleared cache and still received these errors.

  "typescript": "4.4.3",
  "ts-jest": "27.0.5"

Neither isolatedModules: true or diagnostics: false in my tsconfig work for disabling type checking on *.jsx files.

// jest.config.js
module.exports = {
  preset: 'ts-jest',
  testEnvironment: 'jsdom',
  moduleFileExtensions: ['ts', 'js', 'tsx', 'jsx'],
  transform: {
    '^.+\\.(j|t)sx?$': 'ts-jest',
  },
  globals: {
    'ts-jest': { tsconfig: './test.tsconfig.json' },
 },
  moduleDirectories: [ 'node_modules', '<rootDir>../../node_modules' ]
};

My tsconfig (test.tsconfig.json)

{
  "include": ["src"],
  "compilerOptions": {
    "allowJs": true,
    "checkJs": false,
    "noEmit": true,
    "jsx": "react",
    "module": "commonjs",
    "moduleResolution": "node",
    "target": "es6",
    "lib": ["es6", "dom"],
    "baseUrl": "src",
    "strict": false,
    "skipLibCheck": true,
    "declaration": false
  }
}

**Edit: ** it was my fault, ignore me.

My problem was that there were legitimate JavaScript type errors occurring and I assumed it was typescript type checking errors. Sorry about the confusion.

[capaj]

interesting. It only happened once, after that it seems to work correctly. Might be a cache issue.