I didn't want raise this issue in nvim-cmp as it is actually not related to that plugin, more how the sources by @hrsh7th use the after/plugin dir. The problem is that this directory is not something you should use if you expect to allow a plugin be hot loaded, i.e. added to the runtimepath dynamically: for example via packadd.
See this issue vim/vim#1994. after/plugin is not loaded by the builtin package manager and as suggested by a contributor in that issue, this is a directory primarily for users not plugins.
I didn't want raise this issue in
nvim-cmpas it is actually not related to that plugin, more how the sources by @hrsh7th use theafter/plugindir. The problem is that this directory is not something you should use if you expect to allow a plugin be hot loaded, i.e. added to the runtimepath dynamically: for example viapackadd.See this issue vim/vim#1994.
after/pluginis not loaded by the builtin package manager and as suggested by a contributor in that issue, this is a directory primarily for users not plugins.