-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
module 'health' not found #50
Comments
My neovim version is 0.9.0,It should not be supported by the version. |
+1 |
1 similar comment
+1 |
modify the health.lua in clipboard-image plugin local health = vim.health or require "health" instead of local health = require "health" and it worked for me |
Got same issue using neovim v0.9 and v0.10 and on only on macOS 13.3.1 / M1 chip. Exactly same neovim configs work well on macOS 12.# / Intel chip (not sure it's related, but just FYI). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Error 19:45:01 msg_show.lua_error E5108: Error executing lua ...lazy/clipboard-image.nvim/lua/clipboard-image/health.lua:3: module 'health' not found:
no field package.preload['health']
cache_loader: module health not found
cache_loader_lib: module health not found
no file './health.lua'
no file '/opt/homebrew/share/luajit-2.1.0-beta3/health.lua'
no file '/usr/local/share/lua/5.1/health.lua'
no file '/usr/local/share/lua/5.1/health/init.lua'
no file '/opt/homebrew/share/lua/5.1/health.lua'
no file '/opt/homebrew/share/lua/5.1/health/init.lua'
no file './health.so'
no file '/usr/local/lib/lua/5.1/health.so'
no file '/opt/homebrew/lib/lua/5.1/health.so'
no file '/usr/local/lib/lua/5.1/loadall.so'
stack traceback:
[C]: in function 'require'
...lazy/clipboard-image.nvim/lua/clipboard-image/health.lua:3: in main chunk
[C]: in function 'require'
.../lazy/clipboard-image.nvim/lua/clipboard-image/paste.lua:4: in main chunk
[C]: in function 'require'
[string ":lua"]:1: in main chunk
,
I was still able to use it for a period of time, but now there is such an error, which cannot be solved by reinstallation.
The text was updated successfully, but these errors were encountered: