prettierd VS telescope.nvim

First, you need prettierd:

Besides remapping keys, auto-format with prettier (null-ls, ALE, etc) will wrap your code on line break. This might not be desirable for txt files, but it's transparent and fully supported by markdown. It'll also fix things like aligning your markdown tables. There's also prettierd and prettier_d_slim to keep it running as a daemon in the background, which makes the buffer reformatting really snappy.

For react you will need the one for typescript and the eslint lsp is also used in the config to auto fix errors on save. Also this relies on prettierd to be installed globally: https://github.com/fsouza/prettierd

But today I discovered this tool: https://github.com/fsouza/prettierd. This completely solves the issue: the slowness of prettier is due to the overhead of launching the program. This package leaves prettier running as a daemon, which removes the launch overhead (kind of similar to the already famous `eslint_d`).

for telescope.nvim (optional) live grep: ripgrep find files: fd

Here we have a configuration for telescope.nvim, a very popular fuzzy finder.

EDIT: I found what I was looking for https://github.com/nvim-telescope/telescope.nvim and https://github.com/nvim-telescope/telescope-file-browser.nvim

Fuzzy Finder: fzf.vim (for its speed) along with telescope.nvim (for its ecosystem)

Just landed on Telescope.nvim: https://github.com/nvim-telescope/telescope.nvim/pull/2572

This extension allows you to use the power of ast-grep to find code patterns in your editor, using the familiar and awesome interface of telescope.nvim.

telescope.nvim

My solution is using telescope.nvim with lsp extension, and map the vim.lsp.buf.definition keybinding to telescope one https://github.com/nvim-telescope/telescope.nvim