typescript.nvim VS nvim-lsp-file-operations

typescript.nvim will also be archived

typescript.nvim has an option to "Go To Source Definition".

Same question here: how does it compare to typescript.nvim?

Im using this plugin, and here is the code, when for example copy some code, and save the file import all missing files, organize imports and remove unused code automatically:

It depends on your language server. Tssever has this functionality builtin into it, you need typescript.nvim to use it

I would suggest installing jose-elias-alvarez/typescript.nvim. It provides commands like TypescriptOrganizeImports, TypescriptAddMissingImports, TypescriptRenameFile and TypescriptGoToSourceDefinition

Try to use with this typescript.nvim

The options injection system works properly for other languages. So I think this is some kind of tsserver configuration thing I'm missing. I also checked typescript.nvim but it seems to only provide commands like :TypescriptOrganizeImports that I already get using lsp.

I use nvim-lsp-file-operations for this:

Currently, we don't have a separate command for it, but it is supported through the nvim-lsp-file-operations. However, adding a command is certainly possible.

This means that you can easily move files from one folder to another with a few clicks. And all the imports will be automatically refactored. https://github.com/antosha417/nvim-lsp-file-operations

Hey! I made an extension to nvim-tree.lua which is called nvim-lsp-file-operations . It subscribes to events emitted by nvim-tree and automatically applies any necessary workspace edits when performing file operations.