friendly-snippets VS mason-lspconfig.nvim

Those definitely seem to be coming from friendly-snippets, so it seems like it's not being disabled. You can verify this with the :Lazy command to bring up the lazy.nvim menu then checking log or debug to see what is loaded, when, and why.

Here you go :), tested with friendly-snippets lazy loaded (Non lazy-loaded is 500ms)

Snippets for code comments.

I am trying to add snippets for python, i have LuaSnip and friendly-snippets installed, but for some reason it does not load the snippets. This is how i load the plugins:

I just sent [this PR](https://github.com/rafamadriz/friendly-snippets/pull/301) that implements the [full TSdoc specification](https://typedoc.org/guides/overview/) in [friently-snippets](https://github.com/rafamadriz/friendly-snippets). In practice what you get is autocompletion in your typescript comments, which should be a nice of life improvement for most typescript developers.

You mean snippets? If yes, you can try Luasnip and friendly-snippets with nvim-cmp and here's the setup guide. Hope it helps

For example Luasnip with (I guess) friendly-snippets has multi line snippets defined by default. And you can use luasnip with nvim-cmp (read the docs or I guess there’s a YouTube tutorial)

If you copied the config in the readme, then the snippet come from friendly-snippets.

I would recommend lsp-zero, the tsserver lsp provides code actions for auto import. There is auto import when confirming completion as well, I've seen it working with cmp, however I can't remember If that is out of the box behaviour. For snippets, I would go with LuaSnip - It's very versatile snippet engine and it integrates well with many snippet formats. There are specifically react es7 snippet definitions in the friendly-snippets repo which can be used by LuaSnip - https://github.com/rafamadriz/friendly-snippets/blob/main/snippets/javascript/react-es7.json

https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.

pylsp offers an option to install flake8 as an optional plugin and Mason offers a command to install pylsp plugins. I could then install flake8-pytest-style via pip. Then pylsp and flake8 would live in the same Mason environment and flake8-pytest-style would live in my project's environment. I don't know if/how they will communicate with each other.

Personally, i think nvim-lint is the best alternative currently, specially so because it has no dependencies on external binaries. This guide assumes you already have your LSP set up with nvim-lspconfig (or an alternative like lsp-zero). You should also have an way to install the linters you are gonna need, i highly recommend Mason with mason-lspconfig.

Have you set up https://github.com/williamboman/mason-lspconfig.nvim as well?

You can also use https://github.com/williamboman/mason-lspconfig.nvim with nvim-lspconfig to make language server installation closer to installing a vscode extension, in that you just install a language server through mason and it'll be automatically configured for you.

https://github.com/williamboman/mason-lspconfig.nvim - Mason plugin to manage your LSP servers.

I found this GitHub issue: https://github.com/williamboman/mason-lspconfig.nvim/issues/224 I think it could be related, but I'm not sure.

LSP: lspconfig & mason-lspconfig.nvim"