Linting in VS Code not working when using enableProjectDiagnostics
See original GitHub issueI set up a simple deno project with only this file. But the linting is messed up. It looks like the default TypeScript language server is still parsing this file, even though I have installed the extension.
import { cron } from 'https://deno.land/x/deno_cron@v1.0.0/cron.ts';
import { config } from 'https://deno.land/x/dotenv@v2.0.0/mod.ts';
console.log('cron initiated: ', new Date());
cron('*/5 * * * *', async () => {
await fetch("bla")
});
My workspace settings:
{
"deno.lint": true,
"deno.unstable": true,
"deno.enable": true
}
Issue Analytics
- State:
- Created 2 years ago
- Comments:32 (15 by maintainers)
Top Results From Across the Web
Linting Python in Visual Studio Code
To enable third-party linters for additional problem detection, you can enable them by using the Python: Select Linter command and selecting the appropriate ......
Read more >How to make Visual Studio Code check entire project for errors?
1 ) it's too random. Problems appear and disappear by magic. The cursor is flickering. Etc. I would recommend to use the Linter...
Read more >Using Visual Studio Code | Manual - Deno
While developing code in the editor, if the module is not in the cache, you will get a diagnostic like Uncached or missing...
Read more >VS Code tips — Quickly fix all linter errors in a file ... - YouTube
Today's VS Code extension tip: ESLint fix all actions Quickly fix all linter problems for a given ESLint rule or fix all auto...
Read more >ESLint not working in VSCode? Help build a troubleshooting ...
I spend far too much time fighting configuration issues in my toolchain. Most issues I even encounter... Tagged with eslint, webdev, linting ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Enabling project diagnostics for the built in TypeScript server does not enable the same feature for the Deno language server. If there is a desire for the same feature in the Deno language server, that would be a separate request.
This issue only covers the situation where someone has it enabled globally for the built in TypeScript language server, but has enabled Deno for a specifoc workspace. Currently the only workaround would be to disable the feature in the workspace, as it breaks the suppression mechanism of the Deno vscode extension.
Do you have project diagnostics enabled? (
typescript.tsserver.experimental.enableProjectDiagnostics
) That also seems to trigger it for me.