[Bug] From version 2.8.0 the plugin stopped working - Found 0 endpoints

[gi4c0]

Neovim Version

0.11.5

Plugin Version

2.8.0

Framework

NestJS (TypeScript)

Configuration

return {
  "zerochae/endpoint.nvim",
  dependencies = {
    "folke/snacks.nvim",            -- For snacks picker
  },
  cmd = { "Endpoint", "EndpointRefresh" },
  config = function()
    require("endpoint").setup {
        picker = {
            type = 'snacks'
        }
    }
  end,

  keys = {
      { '<leader>se', ':Endpoint<CR>', silent = true, desc = 'Find Endpoints' },
      { '<leader>sEp', ':Endpoint Post<CR>', silent = true, desc = 'Find Endpoints POST' },
      { '<leader>sEP', ':Endpoint Put<CR>', silent = true, desc = 'Find Endpoints PUT' },
      { '<leader>sEr', ':EndpointRefresh<CR>', silent = true, desc = 'Find Endpoints PUT' },
  }
}

What happened?

After updating from 2.7.0 to 2.8.0 it can't find any endpoints showing the errors:

[endpoint.nvim] Scanning endpoints: Found 0 endpoints
No  endpoints found

So I had to downgrade to previous version where it works fine.

Expected behavior

Finds endpoints as usual

Steps to reproduce

Run :Endpoints<CR>

Error logs

[endpoint.nvim] Scanning endpoints: Found 0 endpoints
No  endpoints found

Additional context

No response

[zerochae]

Hi @gi4c0, thanks for reporting this!

I've been investigating the changes between v2.7.0 and v2.8.0. The main changes in v2.8.0
are:

1. Async scanning — find() switched from synchronous to asynchronous execution using
   vim.system
2. Shell input sanitization — Pattern arguments changed from raw string concatenation to
   vim.fn.shellescape() for security
3. Tree-sitter parsing (disabled by default, so this shouldn't be the cause)
4. Progress notifications

The most likely cause is the shellescape() change in rg.lua. NestJS decorator patterns
contain special characters (@, (, )) that may be double-escaped, causing ripgrep to find 0
matches.

I'm looking into it and will follow up with a fix soon.

In the meantime, you can pin to v2.7.0 in lazy.nvim:

  {                                                                                            
    "zerochae/endpoint.nvim",                    
    tag = "v2.7.0",
  }

[zerochae]

I haven't been able to reproduce this on my end — v2.8.0 works fine in my local environment.
Could you provide some additional info to help narrow down the issue?

  1. OS: Windows / Linux / Mac?                                                                
  2. ripgrep version: output of rg --version                                                   
  3. Project structure: Is it a monorepo or a standard single NestJS project?                  
  4. Error details: Could you run :messages in Neovim right after the Found 0 endpoints message
   and share the output?                                                                       

This will help me figure out what's different in your environment. Thanks!

[gi4c0]

Sorry for delay and thanks for putting effort into this!

1. OS: MacOS
2. I updated rg to check with new version but the result is the same

[I] ➜  rg --version
ripgrep 15.1.0

features:+pcre2
simd(compile):+NEON
simd(runtime):+NEON

PCRE2 10.45 is available (JIT is available)

3. Monorepo and single project - doesn't work with both. Monorepo looks something like this:

apps |
          | app1/
                    | src/
                    | package.json
          | app2/
                    | src/
                    | package.json

4. Messages are empty. There's just the notification.

[zerochae]

Hi @gi4c0,
I've removed some code that I suspect may be causing the issue.
Could you test from the fix/64 branch and let me know if it resolves the issue?

  {                                                                                                                                                                 
    "zerochae/endpoint.nvim",                                                                                                                                       
    branch = "fix/64",                                                                                                                                              
  }                                                                                                                                                                 

[gi4c0]

Unfortunately still doesn't work