Closed prdanelli closed 7 months ago
I'm getting a similar error after updating luasnip.
I'm fairly certain this issue occurs because of an unclean update (there may be another luasnip-installation in your runtimepath), or somehow originates from outside luasnip (doubt this honestly, but that error-message is not complete, so don't want to rule that out just yet) since luasnip itself does not contain any reference to the deleted module _caches
.
The former issue often happens due to an unclean transition from packer to lazy.nvim, maybe thats the case here?
The former issue often happens due to an unclean transition from packer to lazy.nvim, maybe thats the case here?
Might be! What's the best way to clear out any old data and start fresh? Should I nuke all the luasnip directories that show up in the stacktrace?
@semanticart I have just had the same problem. I have my nvim config under ~/.config/nvim
so running rm -r ~/.config/nvim/lua/snippets
solved it for me.
You could take a look at your runtimepath
(or even use an API like get_runtime_file (think that's it) to find directories that have a lua/luasnip/init.lua
), if there is more than one entry for luasnip, one of them is certainly at fault :)
Thank you. I'm back to good again with a fresh install 😄
Seems like removing the Lazy entries, cleaning and reinstalling fixe the issue. 👍🏻
Following error when opening Telescope with auto insert mode active.