There's a GitHub issue that discusses the [ts]
token from the errors in a bit more detail. The most relevant comment to this discussion is:
Yes. The TypeScript extension powers our javascript intellisense which is why you see [TS]
in your js file. That only indicates what extension is providing that error.
You can disable this validation itself by adding the following to an appropriate settings.json
file:
"javascript.validate.enable": false
The docs discusses this option a little bit further:
With javascript.validate.enable: false
, you disable all built-in syntax checking. If you do this, we recommend that you use a linter like ESLint to validate your source code.
As noted above, this disables all built-in syntax checking. Although the suggestion is to use something like ESLint instead, there might be another option if you're specifically concerned about the import
/export
errors. You can add a jsconfig.json
file to your project with the following content:
{
"compilerOptions": {
"module": "es2015"
}
}
This instructs VS Code to use the es2015 module syntax (import
/export
), which appears to make it happier.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…