treesitter

Thank you for this amazing plugin! (TJ brought me here)
I found this strange bug that happens for your plugin, but doesn't occur with Tpope's.
Write the following: (I used python for this example)

print("hello world")

When while still in insert mode write: <C-\><C-o>gcc
(<C-\><C-o>) takes you into normal mode for a single command before returning to insert mode)
expecte

It's easy to get lost in a big nested object literal.

What if we added a new query that records the current key of the object the user is focused inside of? It would be best if the query worked at any level of nesting so an object like

const foo = {
  bar: {
    baz: {
      bip: 'bop' // cursor on this line
    }
  }
}

would return {} foo > {} bar > {} baz > {} bip

I

Currently the easiest way to add custom filtering of nodes is to either hook into the validator or the virtual text parser.

It would be nice to have the option to have the option blacklist_targets via the setup() method as an alternative that just provides a table for simplicity.

I don't think we necessarily need to depend on the lspconfig library and can re-write some things to not have to use it.

nvim-metals does not depend on lspconfig.