<p dir="auto">Added in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="614861812" data-permission-text="Title is private" data-url="https://github.com/denoland/deno/issues/5157" data-hovercard-type="pull_request" data-hovercard-url="/denoland/deno/pull/5157/hovercard" href="https://github.com/denoland/deno/pull/5157">#5157</a> but had to be reverted in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="700144044" data-permission-text="Title is private" data-url="https://github.com/denoland/deno/issues/7432" data-hovercard-type="pull_request" data-hovercard-url="/denoland/deno/pull/7432/hovercard" href="https://github.com/denoland/deno/pull/7432">#7432</a> because it breaks <code class="notranslate">.tsbuildinfo</code>.</p>
<p dir="auto">Tracking issue for <code class="notranslate">deno lsp</code> subcommand.</p>
<p dir="auto">Given that a lot of code in <a href="https://github.com/denoland/vscode_deno"><code class="notranslate">vscode_code</code></a> duplicates logic inside <code class="notranslate">deno</code> binary (eg. module resolution algorithm, DENO_DIR path hashing) it becomes obvious that deno should provide its own LSP.</p>
<p dir="auto">Implementing LSP inside the binary should make maintaining the extension easier, as well as it will allow us to provide the same benefits and experience to other editors.</p>
<p dir="auto"><em>This feature is being worked on</em></p>