Performance

[maxcountryman]

Hi, first thanks for putting this plugin together! It's very helpful to have.

I wanted to also report what I think is a performance issue related to the plugin: it seems that when it's installed and detects the Astro filetype scrolling becomes quite choppy. Disable the plugin and the issue goes away.

For context here, I'm using Neovim 0.7.x via tmux 3.2a and kitty 0.25.x. I do have a number of other plugins installed, but this is the first time I've noticed any kind of detectable performance degradation.

If there's any more detail I can provide, I'd be happy to.

[chadoh]

Not sure if it's related, but for me the performance seems great, but some highlighting is off:

I think this might be caused by using TypeScript but not enabling TypeScript in vim-astro.

When I do enable TS, using the following:

let g:astro_typescript = 'enable'

I can't even open the file that contains the above code. The process seems to hang forever!

[maxcountryman]

I ended up foregoing this plugin and using treesitter directly (via lspconfig and mason-lspconfig specifically); it works great and of course the performance of treesitter is just about as good as it gets. I'm not seeing any visual highlight issues like that after using it for the last two weeks.

[ss77a]

Performance doesn't seem to be issue. I've been using a nvimdots setup with excellent initial treeseitter config.

Before I used this plugin with nvchad no performance issues. But wanted to see if I could get path resolve working again

Looking for ideas I came across this https://stackoverflow.com/questions/51272493/resolving-javascript-modules-via-gf-in-vim-when-using-a-webpack-tilde-alias

I think a previous setup I had working was borrowing vscode extensions. The resolve feature has stopped work in vscode too. I'm baffled maybe the link will solve my issues

Just feedback from my experience of the plugin