<p dir="auto"><strong>Is your feature request related to a problem? Please describe.</strong><br>
It's no secret that deno_lint is fast. Like, much, <a href="https://github.com/denoland/deno_lint#performance">much faster than eslint</a>. As such (and as the <a href="https://github.com/denoland/deno_lint/issues/176" data-hovercard-type="issue" data-hovercard-url="/denoland/deno_lint/issues/176/hovercard">deno_lint roadmap</a> heads toward eslint plugin compatibility and autofix), deno will see an increasing number of users and companies adopt deno lint for their linting solution, whether they use node, deno, or any other runtime.</p>
<p dir="auto">Obviously, running lint in CI is nice, but most users want LSP integration, so that they can see lint issues as they write code.</p>
<p dir="auto"><strong>Describe the solution you'd like</strong><br>
If this extension/lsp were to enable users to run the deno lsp <em>purely</em> for linting, <strong>without</strong> disabling normal typescript language features, and without enabling <em>any</em> other deno lsp features, we could have a hybrid world where users who use node, bun, etc, could use deno lint to great success.</p>
<p dir="auto">This would increase adoption and awareness of deno tooling, and make other engineers happy.</p>
<p dir="auto">Essentially, I wish the deno vscode extension would let us do <code class="notranslate">"deno.enable": false, "deno.lint": true</code>. In this sense, we get the linting features of the deno lsp without turning off visual studio code typescript language features.</p>
<p dir="auto">Please consider this request! Let me know if I can provide any further information.</p>
<p dir="auto"><strong>Is your feature request related to a problem? Please describe.</strong></p>
<p dir="auto">I wanted to use deno linter instead of eslint in VSCode for the project that is not deno-specific. I run <code class="notranslate">deno lint</code> on my project's code and the issues it finds are very useful for me, but I hate fixing them from the console, and I would greatly appreciate to see them as... well... lint output in the VSCode. But it seems it does not work :(<br>
Is it possible to have this functionality in this extension?</p>
<p dir="auto">My workspace config I tried to use:</p>
<div class="highlight highlight-source-json notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="{
    &quot;deno.enable&quot;: false, // As I don't want to use deno. Deno will not handle imports (standard imports; dependencies defined in package.json)
    &quot;deno.lint&quot;: true,
    &quot;eslint.enable&quot;: false
}"><pre class="notranslate">{
    <span class="pl-ent">"deno.enable"</span>: <span class="pl-c1">false</span>, <span class="pl-ii">// As I don't want to use deno. Deno will not handle imports (standard imports; dependencies defined in package.json)</span>
    <span class="pl-ent">"deno.lint"</span>: <span class="pl-c1">true</span>,
    <span class="pl-ent">"eslint.enable"</span>: <span class="pl-c1">false</span>
}</pre></div>
<p dir="auto">After restarting VSCode I don't see any linting messages in VSCode. It looks like <code class="notranslate">deno.enable: false</code> turns extension off.</p>
<p dir="auto">And screenshot showing that indeed it's not working:<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/516709/152682237-4311eeae-0768-4a0b-8c99-0498a1a92193.png"><img src="https://user-images.githubusercontent.com/516709/152682237-4311eeae-0768-4a0b-8c99-0498a1a92193.png" alt="image" style="max-width: 100%;"></a></p>
<p dir="auto"><strong>Describe the solution you'd like</strong></p>
<p dir="auto">I would love to use deno lint in the VSCode without enabling deno support. It should be possible, because <code class="notranslate">deno lint</code> works fine from the terminal.<br>
And I would love to see these warning/errors marks directly in the code</p>