Vim, Neovim, WezTerm, TMUX, zsh, Ghostty, and Git configs.

3 Open Issues Need Help Last updated: Jun 19, 2025

Open Issues Need Help

View All on GitHub

AI Summary: Debug why the VTSLS language server in Neovim is not reporting TypeScript errors defined in a `tsconfig.app.json` file, despite the errors being correctly identified by the TypeScript compiler when run from the command line. This involves investigating the Neovim configuration, the VTSLS setup, and potentially the `tsconfig.json` and `tsconfig.app.json` files to ensure proper project configuration and communication between the language server and the editor.

Complexity: 4/5
bug documentation help wanted question

Vim, Neovim, WezTerm, TMUX, zsh, Ghostty, and Git configs.

Lua

AI Summary: The task is to debug and fix a bug in a Neovim configuration where the vtsls language server incorrectly identifies the package manager due to a globally installed bun.lockb file, even when other lockfiles (pnpm, yarn, npm) are present in the project directory. The solution involves refining the package manager detection logic within the vtsls configuration to prioritize lockfiles within the project's root directory and avoid false positives from globally installed tools.

Complexity: 4/5
bug documentation help wanted

Vim, Neovim, WezTerm, TMUX, zsh, Ghostty, and Git configs.

Lua

AI Summary: Debug and resolve why lualine.nvim is loading eagerly during Neovim startup, potentially by identifying the plugin causing premature loading and implementing a lazy-loading solution or a cleaner deferral mechanism. This involves analyzing the Neovim configuration, plugin dependencies, and startup sequence.

Complexity: 4/5
bug documentation help wanted

Vim, Neovim, WezTerm, TMUX, zsh, Ghostty, and Git configs.

Lua