If you find yourself here and none of the other answers is solving the problem, check to make sure that you haven't set maxNodeModuleJsDepth. If you have allowJs enabled this option lets TypeScript attempt to infer types from modules in node_modules, and skipLibCheck doesn't have any effect on that, because it's reading javascript files and not type declarations. The default setting for maxNodeModuleJsDepth is 0, and in the vast majority of cases that's what you want (and you should prefer using @types packages instead of turning this on).

在tsconfig.json中设置"skipLibCheck": true

If you find yourself here and none of the other answers is solving the problem, check to make sure that you haven't set maxNodeModuleJsDepth. If you have allowJs enabled this option lets TypeScript attempt to infer types from modules in node_modules, and skipLibCheck doesn't have any effect on that, because it's reading javascript files and not type declarations. The default setting for maxNodeModuleJsDepth is 0, and in the vast majority of cases that's what you want (and you should prefer using @types packages instead of turning this on).

如果你在这里，但下面的方法对你都不起作用:

❌ Updgrade/downgrading typescript version (NOTE: When you run the tsc command, the globally installed typescript version is used as the compiler. So even if you have the latest typescript version in your package.json, you will have to upgrade typescript globally. With npm thats npm install typescript@latest -g ) ❌ Adding/Editing tsconfig options: target, types, include, exclude, allowJs, skipLibCheck ❌ npm update ❌ Deleting node_modules && npm i ❌ Deleting package-lock (don't do that btw) && npm i

我想从typescript配置文档中留下这个链接给你: 这(“类型”)会影响什么?

有了这些知识，这为我解决了问题:

查看在运行tsc时是哪个模块导致了日志中的错误。(对我来说是node_modules/mongoose/types/*，所以mongoose是罪魁祸首。) 将您在ES6中导入的所有该模块转换为commonjs的require()。(在我的例子中，import mongoose from 'mongoose'—> const mongoose = require('mongoose'))

我希望这能解决你的问题

在"compilerOptions"中添加一个空的"types"选项:

{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "sourceMap": true,
    "strict": false,
    "noImplicitAny": false,
    "strictPropertyInitialization": false,
    "esModuleInterop": true,
    "types": []
  },
  "include": [
    "src/*"
  ],
  "exclude": [
    "node_modules",
    "./node_modules",
    "./node_modules/*",
    "./node_modules/@types/node/index.d.ts",
  ]
}

从https://www.typescriptlang.org/docs/handbook/tsconfig-json.html

@types, typeRoots and types By default all visible “@types” packages are included in your compilation. Packages in node_modules/@types of any enclosing folder are considered visible; specifically, that means packages within ./node_modules/@types/, ../node_modules/@types/, ../../node_modules/@types/, and so on. ... Specify "types": [] to disable automatic inclusion of @types packages. Keep in mind that automatic inclusion is only important if you’re using files with global declarations (as opposed to files declared as modules). If you use an import "foo" statement, for instance, TypeScript may still look through node_modules & node_modules/@types folders to find the foo package

快速补救是跳过检查

{
  "compilerOptions": {
    "skipLibCheck": true
  },
}