use of rtp to include $HOME/dotfiles/lua - should this work?

[EdmundsEcho]

I'm hoping to include my ~/dotfiles/lua as a source of modules. I thought the following would work (I have tried with reset true or false).

require("lazy").setup( { 
      { import = "cape.plugins" }, 
      { import = "cape.plugins.lsp" } 
    }, 
    rtp = {
      reset = true, 
      ---@type string[]
      paths = {
        vim.fn.stdpath("config") .. "/lua",
        vim.fn.expand("$HOME") .. "/dotfiles/lua"
      }, 
    },
})

I can append to the package.path using:

package.path = package.path .. ';' .. root .. "/lua/?.lua"
package.path = package.path .. ';' .. root .. "/lua/?/init.lua"

but that does not let me reference anything beyond the first layer of directories (e.g., first.next does not work).

[folke]

Should work, just skip the /lua part

[EdmundsEcho]

I get the the empty specs error:

Error detected while processing /Users/edmund/.config/nvim/init.lua:
No specs found for module cape.plugins
No specs found for module cape.plugins.lsp

paths = {
        vim.fn.expand("$HOME") .. "/dotfiles"
      }, 
      

My home directory is : ~/dotfiles/lua/cape/plugins

I structured the home directory to include lua thinking this is required for hosting lua modules.

[folke]

no that wont works. I though you meant something else

[EdmundsEcho]

In general, loading the files as modules is straightforward. It's getting lazy to import plugins from elsewhere which is the challenge. I can confirm that neovim's rtp is pointing where I want it to.

This all said, when I put a symlink in ~/.config/nvim/lua/cape that points to ~/dotfiles/lua/cape lazy finds the plugins.