Confusion between Lazy Loading Vs after/plugin/*

[vignesh0025]

Hi,

First of all thank you for this awesome plugin.

I am totally confused between after/plugin/* and lazy loading options in Lazy.nvim.

suppose I have the following case:

init.lua

lazy.setup({   
  'abcd/treesitter',
  event = 'BufEnter'
}, {})

after/plugin/treesitter.lua

require("treesitter").setup()

As per lazy.nvim, treesitter is lazy loaded when BufEnter occurs. But now that I placed "treesitter.lua" in after/,
Will lazy.nvim run treesitter.lua inside after/ directory when BufEnter event occurs (as per lazy loading rule) ?
OR
Will treesitter.lua be executed at start-up since I placed it under after/ and it won't be lazy loaded as per rules of after/ ?

Thank you

[folke]

This all works as it works with regular Neovim packages. So the /after files in your rtp are always sourced during startup. Not sure if I understand your question.

If you do a require("treesitter") in an /after file, then that would basically load treesitter at startup.

If you want to lazy-load it, you need to do your config in config() as is explained in the docs.

[vignesh0025]

Thank you. That answered my question.
If I want to lazy load, I have to require the plugin in config(). Having the require in rtp path will simply load it at startup and won't lazy load.
Thank you!