Paweł Mizio

You right I also spotted this bug, fix here: https://github.com/pmizio/typescript-tools.nvim/pull/222, let me know if it helps if yes I'll merge it.

If you will be able to provide more info and steps to reproduce I will do my best to fix it. I use this in my commercial job daily and...

@Gelio @roguesherlock @macstr1k3r So I added feature which may help debug this: ``` :lua require("typescript-tools.api").save_snapshot_to("snapfile.js") ``` this should save current tsserver in memory representation of affected file you can compare...

@Gelio So, I started to dig in this but without any reproduction is hard to debug it. But I started to look for some nvim diagnostic api and I bumped...

Probably second solution will be to use builtin nvim pull diagnostic but its implementation miss `relatedDocuments` functionality which is necessary for tsserver. In free time I'll try to extend this...

@gmmoose20 It shouldn't be like that, besides nvim deduplicate same diagnostics from one server. It looks like you have second one which is running for example standard tsserver from lspconfig....

If it isn't listed in `:LspInfo` this mean it is correctly disabled. Followup question, you have it duplicated always and every diagnostic message is duplicated or is it accideutialy -...

Weird, I'll install LazyVim distro and check it with your configuration. @gmmoose20 can you post how you configure my plugin?

@gmmoose20 ok so i installed lazyvim to check it and fill my understanding of situation, you have both lazyvim's setting ` { import = "lazyvim.plugins.extras.lang.typescript" },` and my plugin in...

@gmmoose20 Can you make some minimal repo with config which presents error? I cannot reproduce it, tried to install lazyvim by cloning it into my `.config/nvim` then I just created...