jester VS treesitter-unit

I use nvim-dap[1] in combination with jester[2] (by me) to run and debug Jest tests in my project, it works perfectly.

[1]: https://github.com/mfussenegger/nvim-dap

[2]: https://github.com/David-Kunz/jester

For JavaScript with Jest, I created Jester to run and debug tests: https://github.com/David-Kunz/jester

Mostly use it with tests and jester

I use only jester for DAP. Would like to found also something new for neovim.

Hi, I built a plugin for Jest: https://github.com/David-Kunz/jester

Hi, I created jester to easily run and debug Jest tests.

It's also relatively easy to write plugins based on the parsed AST. I wrote treesitter-unit[1] making it easy to select/modify the subtree of the selection.

[1]: https://github.com/David-Kunz/treesitter-unit

I built a plugin to select units of tree-sitter objects https://github.com/David-Kunz/treesitter-unit

To delete/yank the node, the combination would be `diu`, using this plugin: https://github.com/David-Kunz/treesitter-unit

Hi, I also think treesitter-textobjects are a bit overspecific, that's why I created https://github.com/David-Kunz/treesitter-unit/ .

In this video I create a Neovim plugin called 'treesitter-unit' using Lua. You can find the final plugin here: https://github.com/David-Kunz/treesitter-unit/

I tried it with operator mode maps and it works perfectly! I updated the README to include: vim.api.nvim_set_keymap('o', 'x', ':lua require"treesitter-unit".select()', {noremap=true})