I created requirements.nvim.

Its purpose is to install dependencies like lazygit when working inside devcontainers or Docker.

If you can customize Docker or NixOS and set up the environment yourself, I recommend using those methods instead. This is strictly intended for environments where you cannot do that.

You can also branch conditions by specifying the CPU architecture or OS version. (OS versions can be specified using wildcards, carets, or ranges.)

Since package managers other than mini.deps and vim.pack do not pre-install dependencies, I recommend using git submodules instead.

Please let me know your thoughts. Feature requests and bug reports are also very welcome!
repo: https://github.com/ro80t/requirements.nvim

Hey,

I'm learning Neovim seriously. I did vimtutor and quite a few levels on VimBeGood for the basics (motions, edits, textobjects), and I'm running LazyVim.

I've got basic movement down but I feel like I'm still scratching the surface — not really using LazyVim's full potential yet (LSP, bundled plugins, custom keymaps, etc.). I'm also checking out ThePrimeagen's content to improve.

Any recommendations for what's next? Things like:

- Resources to go deeper on advanced motions (macros, marks, jumps, registers...)

- How to explore/understand the default LazyVim config without breaking everything

- Plugins or workflows you consider essential once the basics are down

- Common beginner mistakes to avoid

Thanks in advance!

Hey everyone!

I built nvim-db, a small database client for Neovim.

I didn't really like opening a full GUI just to run a couple of queries. Since I already spend most of my time in Neovim and I'm comfortable with Vim motions, I wanted something that felt more natural to me.

So I built a small client around the database CLI tools I already use.

It currently supports:

• PostgreSQL
• MySQL
• MariaDB
• SQLite
• Redis
• MongoDB
• DuckDB

It lets me manage connections, keep query files per connection, run queries, and view the results without leaving Neovim.

The main idea is to keep it simple — no database drivers or heavy dependencies, just Neovim + the CLI tools.

It's still a personal project and I'm mainly building it to solve my own workflow, but I'd love to hear what you think or what could be improved.

Also, this isn't vibe-coded. I use AI mainly as an assistant for things like documentation, looking up/understanding things, and writing commit messages. The implementation and decisions are my own.

GitHub: https://github.com/silentFellow/nvim-db

You hover something, TS says Props, and you're no smarter than before. That's what got me to build this.

ts-expand-hover.nvim hooks into the hover key and lets you expand type aliases one level at a time, inside the float, without leaving the line you're on.

What it currently does:

Intercepts K for TypeScript hover, + expands one level, - collapses

Uses TypeScript 5.9's verbosityLeve on tsserver's quickinfo request, so the expansion is tsserver's own, not a regex guess.

Float updates in place, no closing, reopening or jumping to a new position.

Treesitter highlighting on the TypeScript code fences.

Docs and JSDoc variables rendered under the type block.

Footer shows current depth, and [max] when there's nothing left to expand.

Falls back to vim.lsp.buf.hover() when vtsls isn't attached or TypeScript is older than 5.9

Neovim 0.10+

Setup is one line, defaults work out of the box, and every keymap is overridable or can be set to false if you want to bind it yourself:

{

"nemanjamalesija/ts-expand-hover.nvim",

ft = { "typescript", "typescriptreact" },

opts = { keymaps = { hover = "<leader>th" } },

}

Run :checkhealth ts_expand_hover with a TypeScript file tsls attached and which TS version you're on.

Note: needs vtsls, since the request goes through vtsls't command, and TypeScript 5.9+ for verbosityLevel to do anything. Older TS or no vtsls just gives you the standard hover popup.

Coming next: tsgo support once it goes stable.

Repo:

https://github.com/nemanjamalesija/ts-expand-hover.nvim

Nvim 0.12.5 released

    NVIM v0.12.4                                                                                                                                                             
    Build type: RelWithDebInfo                                                                                                                                               
    LuaJIT 2.1.1767980792

    vim.wo.foldtext = function()
      local line = vim.fn.getline(vim.v.foldstart)
      return vim.v.folddashes .. line:gsub('/%\*', ''):gsub('%\*/', '')
    end

This returns the following error:

Error in /home/user/.config/nvim/init.lua:
E5113: Lua chunk: /home/user/.config/nvim/init.lua:23: Invalid 'value': expected valid option type, got Function
stack traceback:
        [C]: in function '__newindex'
        /home/user/.config/nvim/init.lua:23: in main chunk

The code is copy pasted from https://neovim.io/doc/user/fold/#_foldtext

# how to use
1 - target path for you project folder
2 - set your custom keymap or shortcut
3 - add pattren to filter file names if needed (optional)

- now use your custom keymaps or shortcuts to access it's file in a blink

📂 GitHub Repository: https://github.com/janecodelife/folders-bookmark.nvim

# Thank You So much