4 ms·
I had attempted to use Deno not long ago, but I learned that (apparently, I might be wrong) you can only get proper intellisense/error checking support if you'r
by nozzlegear 5y ago
I had attempted to use Deno not long ago, but I learned that (apparently, I might be wrong) you can only get proper intellisense/error checking support if you're using a VS Code extension. I write my code in Vim/Neovim almost exclusively, and the import declarations really screwed up my TypeScript plugin; it didn't know how to handle the URLs and so I had no intellisense/error checking.
I gave up after searching around for a few minutes and learning that for now I'd need to use VS Code to write Deno code, if I want those features.
- 91edec 5y agoIf you're using coc you can add the coc-deno extension and initialize the project with `CocCommand deno.initializeWorkspace`.
- nozzlegear 5y agoThanks! I didn't know about the coc extension, I'll give that a try.
- choward 5y agoI have to believe that you leaving the "-deno" off of "coc-deno extension" was intentional which I find to be pretty funny.
- phil294 5y agoNeovim apparently supports the LSP protocol natively, so could you please explain why CoC is necessary?
- chana_masala 5y agoFrom the last I saw, coc is still more feature rich than native LSP in Neovim.
- brundolf 5y agoIt does suck that it can’t use standard typescript tooling because of a couple of small, key, breaking-differences (mainly the import path style, to my understanding). I don’t think they could have done it any differently, and with enough traction the ecosystem support is a solvable problem, but it’s still a shame.
- ravenstine 5y agoI agree, though I do think that Deno's import paths are more correct than Node.js or tsc. I'm not exactly sure sure why official Typescript can't support both by now.