typescript :为什么 Visual Studio 代码不报告与命令行 tsc 相同的错误?

标签 typescript visual-studio-code eslint typescript-eslint

如果我故意在我的代码中打错字,我会得到一个错误。这是正确的代码:

declare const State: TwineState;

如果我删除最后一个字符,然后在命令行上键入 tsc,则会出现以下错误:
tsc/prod.spec.ts:7:22 - error TS2304: Cannot find name 'TwineStat'.

7 declare const State: TwineStat;

但是 Visual Studio Code 似乎没有意识到有任何错误。

enter image description here

我如何让我的编辑器向我显示 tsc 命令识别的相同错误?我对所有这些技术都很陌生,所以我不知道哪些信息有助于排除故障,但这是我的配置文件:

包.json:
{
...
  "version": "1.0.0",
  "main": ".webpack/main",
  "scripts": {
    "compile-typescript": "tsc && cp tscbuild/prod.js story/",
    "lint": "eslint tsc/** --fix",
    "test": "npm run lint && ts-node node_modules/jasmine/bin/jasmine && npm run compile-typescript ..."
  },
  "keywords": [],
...
  "devDependencies": {
    "@types/jasmine": "^3.5.9",
    "@types/node": "^13.9.1",
    "@typescript-eslint/eslint-plugin": "^2.24.0",
    "@typescript-eslint/parser": "^2.24.0",
    "eslint": "^6.8.0",
    "eslint-plugin-testcafe": "^0.2.1",
    "jasmine": "^3.5.0",
    "testcafe": "^1.8.2",
    "ts-node": "^8.6.2",
    "typescript": "^3.7.0"
  },
  "dependencies": {}
}

tsconfig.json:
{
  "compilerOptions": {
    /* Basic Options */
    // "incremental": true,                   /* Enable incremental compilation */
    "target": "es5",                          /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017', 'ES2018', 'ES2019', 'ES2020', or 'ESNEXT'. */
    "module": "commonjs",                     /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', 'es2020', or 'ESNext'. */
    "lib": ["es6","dom"],                           /* Specify library files to be included in the compilation. */
    "allowJs": false,                         /* Allow javascript files to be compiled. */
    // "checkJs": true,                       /* Report errors in .js files. */
    // "jsx": "preserve",                     /* Specify JSX code generation: 'preserve', 'react-native', or 'react'. */
    // "declaration": true,                   /* Generates corresponding '.d.ts' file. */
    // "declarationMap": true,                /* Generates a sourcemap for each corresponding '.d.ts' file. */
    // "sourceMap": true,                     /* Generates corresponding '.map' file. */
    // "outFile": "./",                       /* Concatenate and emit output to single file. */
    "outDir": "tscbuild",                        /* Redirect output structure to the directory. */
    "rootDir": "tsc",                         /* Specify the root directory of input files. Use to control the output directory structure with --outDir. */
    // "composite": true,                     /* Enable project compilation */
    // "tsBuildInfoFile": "./",               /* Specify file to store incremental compilation information */
    // "removeComments": true,                /* Do not emit comments to output. */
    // "noEmit": true,                        /* Do not emit outputs. */
    // "importHelpers": true,                 /* Import emit helpers from 'tslib'. */
    // "downlevelIteration": true,            /* Provide full support for iterables in 'for-of', spread, and destructuring when targeting 'ES5' or 'ES3'. */
    // "isolatedModules": true,               /* Transpile each file as a separate module (similar to 'ts.transpileModule'). */

    /* Strict Type-Checking Options */
    "strict": true,                           /* Enable all strict type-checking options. */
    "noImplicitAny": true,                    /* Raise error on expressions and declarations with an implied 'any' type. */
    "strictNullChecks": true,              /* Enable strict null checks. */
    "strictFunctionTypes": true,           /* Enable strict checking of function types. */
    "strictBindCallApply": true,           /* Enable strict 'bind', 'call', and 'apply' methods on functions. */
    "strictPropertyInitialization": true,  /* Enable strict checking of property initialization in classes. */
    // "noImplicitThis": true,                /* Raise error on 'this' expressions with an implied 'any' type. */
    "alwaysStrict": true,                  /* Parse in strict mode and emit "use strict" for each source file. */

    /* Additional Checks */
    "noUnusedLocals": true,                /* Report errors on unused locals. */
    // "noUnusedParameters": true,            /* Report errors on unused parameters. */
    "noImplicitReturns": true,             /* Report error when not all code paths in function return a value. */
    "noFallthroughCasesInSwitch": true,    /* Report errors for fallthrough cases in switch statement. */

    /* Module Resolution Options */
    // "moduleResolution": "node",            /* Specify module resolution strategy: 'node' (Node.js) or 'classic' (TypeScript pre-1.6). */
    // "baseUrl": "./",                       /* Base directory to resolve non-absolute module names. */
    // "paths": {},                           /* A series of entries which re-map imports to lookup locations relative to the 'baseUrl'. */
    // "rootDirs": [],                        /* List of root folders whose combined content represents the structure of the project at runtime. */
    // "typeRoots": [],                       /* List of folders to include type definitions from. */
    // "types": [],                           /* Type declaration files to be included in compilation. */
    // "allowSyntheticDefaultImports": true,  /* Allow default imports from modules with no default export. This does not affect code emit, just typechecking. */
    "esModuleInterop": true,                  /* Enables emit interoperability between CommonJS and ES Modules via creation of namespace objects for all imports. Implies 'allowSyntheticDefaultImports'. */
    // "preserveSymlinks": true,              /* Do not resolve the real path of symlinks. */
    // "allowUmdGlobalAccess": true,          /* Allow accessing UMD globals from modules. */

    /* Source Map Options */
    // "sourceRoot": "",                      /* Specify the location where debugger should locate TypeScript files instead of source locations. */
    // "mapRoot": "",                         /* Specify the location where debugger should locate map files instead of generated locations. */
    // "inlineSourceMap": true,               /* Emit a single file with source maps instead of having a separate file. */
    // "inlineSources": true,                 /* Emit the source alongside the sourcemaps within a single file; requires '--inlineSourceMap' or '--sourceMap' to be set. */

    /* Experimental Options */
    // "experimentalDecorators": true,        /* Enables experimental support for ES7 decorators. */
    // "emitDecoratorMetadata": true,         /* Enables experimental support for emitting type metadata for decorators. */

    /* Advanced Options */
    "resolveJsonModule": true,                /* Include modules imported with '.json' extension */
    "forceConsistentCasingInFileNames": true  /* Disallow inconsistently-cased references to the same file. */
  }
}

.eslintrc.js:
module.exports = {
  env: {
    browser: true,
    es6: true,
    node: true,
    jasmine: true,
  },
  "extends": [
    "eslint:recommended",
    "plugin:@typescript-eslint/recommended",
    "plugin:testcafe/recommended"
  ],
  globals: {
    Atomics: "readonly",
    SharedArrayBuffer: "readonly"
  },
  parser: "@typescript-eslint/parser",
  parserOptions: {
    ecmaVersion: 2018,
    project: "./tsconfig.json",
  },
  plugins: ["@typescript-eslint", "testcafe"],
  rules: {
    quotes: ["error", "double"],
    "no-plusplus": ["off"],
    "@typescript-eslint/camelcase": ["off"]
  }
};

最佳答案

发生这种情况可能有多种原因。这有时会发生在我身上,我无法解释为什么会发生这种情况,但我注意到 incremental tsconfig.json 中的功能/标志可能会导致转译器缓存会导致这些差异的过时数据。看来 VSCode 可能不使用 incremental缓存数据和命令行。
有两种方法可以测试和解决这个问题。一种是将 tsconfig.json 中的增量标志翻转为 false .完成此操作后,错误将出现在命令行上。问题是当你把它翻回 true 时然后这些错误就会消失。另一个选项是删除您的 outDir - 通常被称为 dist/build/或类似的东西。
我尚未确认的第三个选项是删除 tsconfig.tsbuildinfo仅文件通常位于 outDir 中以及。 tsconfig.json 中有一个设置,名为 tsBuildInfoFile这将将此文件重定向到您为该 Prop 指定的任何值,因此如果您在 outDir 中找不到它,请尝试该位置。

关于 typescript :为什么 Visual Studio 代码不报告与命令行 tsc 相同的错误?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/60803223/

相关文章:

reactjs - 为什么 React.FunctionComponenent 优于传统的函数定义?

jquery - 使用Typescript(Angular 8)一个接一个地旋转木马

node.js - 如何在 JSON 文件中搜索特定位置?

visual-studio-code - 更改 vscode-icons 上的默认文件扩展名图标不起作用

angular - Angular 4 中的长轮询

Angular2 事件发射器未得到处理

javascript - JSDoc 对解构参数的注释在 VSCode 中不起作用

ecmascript-6 - 导入的 ESLint 规则错误

javascript - 导入 `spyOn` 函数摆脱 'not defined' eslint 错误

javascript - eslint 对象简写错误,传入变量