tree-sitter-typescript VS vim-scriptease

Now, let's dive into some practical editing functions implemented using Tree-sitter. Keep in mind that all the functions are specific to the tree-sitter-typescript parser and only work in the Emacs 29 built-in tsx-ts-mode.

I believe goto_next_test requires support from the tree-sitter parser, specifically tree-sitter-javascript in the case of JS and tree-sitter-typescript in the case of TS.

If you need to do efficient AST operations, have you considered treesitter? There is a typescript grammar available https://github.com/tree-sitter/tree-sitter-typescript

I am curious though, why did you write your own indentation tool? (It works super well btw, amazing work) I thought tree-sitter supported tsx (and found repos like this) so just wondering if you tried those and they didn't work so you wrote your own.

Please have a look at it - https://github.com/tree-sitter/tree-sitter-typescript/issues/177

You can see a much more in-depth version at https://github.com/tree-sitter/tree-sitter-typescript or https://github.com/tree-sitter/tree-sitter-rust

I use tpope/vim-scriptease's :Messages instead.

Another great tool is the Scriptnames command from the vim-scriptease plugin. It dumps the output of :scriptnames into the quickfix list, letting you open all the files vim is reading to help with troubleshooting.

And the tpope extension comes in handy: https://github.com/tpope/vim-scriptease

As you continue your journey into vim plugin dev, I'd recommend vim-lookup and vim-scriptease.

This seems related to the g= mapping from vim-scriptease. I personally also have the following two mappings defined in ftplugin/vim.vim:

FYI, tpope/vim-scriptease provides this bound as an operator g=. You may want to read that implementation to see what you can learn more advanced techniques for writing vimscript. With the operator, you can g=W to convert the WORD to a solved expression.