xbase VS pycodestyle.nvim

However I can't seem to find where this argument is being passed in from. I'm using the plugin xbase (https://github.com/kkharji/xbase/) and it doesn't have this string anywhere in the project. It seems like other people have been able to get it running.

You can follow the discussion here: https://github.com/kkharji/xbase/issues/178

I think an excellent example is https://github.com/xbase-lab/xbase/blob/master/Cargo.toml

Checkout Release notes for a comprehensive list of features and bug fixes.

I've added to be support in the next minor release, feel free to subscribe to the issue get updates https://github.com/tami5/xbase/issues/65

With that said, there is still a use for remote plugins: if you really need a libraries from that ecosystem, and you would have those libraries anyway, then there is no harm done. I have a plugin called pycodestyle.nvim which makes your Pycodestyle linter configuration available in Neovim. That way I can use my linter settings as my editor settings per project, no need to keep separate settings in sync. If I want to use that plugin I need Pycodestyle installed anyway, and if Pycodestyle is not available to plugin stays dormant.

Not really. There is exactly one legitimate use case for writing plugins in something other than Lua or Vim script: if you want to use libraries written in that language. For example, I have a plugin named pycodestyle.nvim which is written in Python because it uses the Pycodestyle library to figure out the user's linter configuration. If I wanted to do it in Lua I would basically have to re-implement a major part of Pycodestyle myself, which would be a pointless waste of time. And people who use that plugin already have Pycodestyle installed anyway, so it's not an extra dependency.

Link. When I write Python I usually have pycodestyle as my linter, and this got me thinking: If I already have a linter configuration for a project, why not just use the linter configuration as my editor configuration as well? The linter configuration is useful to others even if they use a different editor and I don't have to duplicate it in a local vimrc or editorconfig file. I can just use what I already have.