`deno lsp` stops working
See original GitHub issue@fannheyward definition jumping is now possible, but there may be other problems. The situation is such that the deno lsp environment is broken after the definition jump. 😦
Repro
- definition jump
CTRL-O
to return to the previous buffer
Capture
https://user-images.githubusercontent.com/188642/146353966-2d6b4995-28a2-4013-a60f-f7d6570b7879.mp4
_Originally posted by @yaegassy in https://github.com/fannheyward/coc-deno/issues/135#issuecomment-995634535_
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How do you configure Deno LSP? : r/neovim - Reddit
As in the processes displayed in the System Resources are gone. However, Deno LSP ( denols ) process keeps running after exiting the...
Read more >How to Resolve LSPs for Deno Projects in Neovim
By creating an empty deno.json file at the root of my Deno projects, the Neovim buffer will make sure that the proper LSP...
Read more >Set up your environment | Manual - Deno
When installed, it will connect to the language server built into the Deno CLI. Because most people work in mixed environments, the extension...
Read more >Deno LSP does not work for .tsx files ("Typescript JSX" file type)
What is the expected result? With the new Deno LSP support, import maps work perfectly in .ts files. However, they do not work...
Read more >Solve nvim lsp denols vs tsserver clash - DEV Community
Tagged with neovim, lsp, deno, typescript. ... as it would not work for when you don't have a Deno project, but have no...
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
@yaegassy make a fix in v3.9.3, please give a try.
I think it’s a great idea. I have confirmed that this issue has been resolved in my environment.