Error message appearing at every initialization - "No specs found for module custom.plugins"

[Stopfield]

Describe the bug After executing nvim, the following error appears every time:

Error detected while processing .../.config/nvim/init.lua
No specs found for module custom.plugins
All parsers are up to date

This doesn't impede nvim to work, but it's really annoying.

To Reproduce Steps to reproduce the behavior:

1. Install nvim
2. Copy the init.lua file into .../config/nvim/
3. Run the first installation
4. The prior message will appear

Desktop (please complete the following information):

• OS: Linux Mint 21.1 x86_64
• Terminal: gnome-terminal (using bash 5.1.16)

** Neovim Version **

• NVIM v0.8.3

More info about the version:

• Build type: Release
• LuaJIT 2.1.0-beta3

[TheSleepingAssassin]

I encountered the same error, after browsing the config for a bit it was an easy fix comment the code on line 189 which says { import = 'custom.plugins' }, This error is produced when there are not already any packages located in lua/custom/plugins. Commenting that line should be an easy fix.

[Stopfield]

Thanks! Should we leave the issue open? Maybe, we could use some automated function to detect custom plugins beforehand

[joaco05]

I think that we should i also ran into the same problem

[arjun7965]

I faced the same issue. Is there a fix for this?

[simon-liebehenschel]

I faced the same issue. Is there a fix for this?

The fix is to clone a whole repository, and not only init.lua. Or do what is described above https://github.com/nvim-lua/kickstart.nvim/issues/204#issuecomment-1446880068

[SiddharthReddy30]

i got the same error

[Welding-Torch]

same error

[SiddharthReddy30]

Just comment out line 189, you will be good. I just submitted a fix with PR#263 hopefully they merge it.

[feoh]

Hiya! The problem here is showcased in your steps to reproduce.

You must copy the entirety of the kickstart.nvim into your ~/.config/nvim in order for it to work, not just init.lua.

Closing.

[nPHYN1T3]

"You must copy the entirety of the kickstart.nvim into your ~/.config/nvim in order for it to work, not just init.lua."

Statements like this make me feel like I'm losing my mind. I read the install README, I watched the video and there is no mention of "copy the entirety of the kickstart.nvim" unless I've read so much everything has blurred into vague nothingness that just hits my eyes and vanishes before it's processed.

The video shows just toss the init.lua in there and start nvim. So what are these other magical files? I mean there are no releases so am I to assume I'm just supposed magically know to copy README.md LICENSE.md stylua.toml .gitignore lua doc ISSUE_TEMPLATE? If I grab it all as a zip the name is kickstart.nvim-master.zip. Will that work or do I need to remove -master.zip? Perhaps a tad more explanation would help. This all seems a bit like "Written by someone who knew for those that know." rather than written for someone who doesn't know. The "Effective Neovim: Instant IDE" video also just shows toss in the init.lua.

As a fun addition I put kickstart.nvim in my nvim folder removing -master.zip. So I have ~/.config/nvim/kickstart.nvim <-- zip ~/.config/nvim/init.lua ...still Error detected while processing ~/.config/nvim/init.lua: No specs found for module custom.plugins

If I rename the zip to have .zip then extract and rename the extracted folder to simply kickstart.nvim and run nvim again...same error.

Only way this works is cloning the git. Which then also shows you do not want a folder kickstart.nvim but rather all the files from it in the same root folder (~/.config/nvim) as the init.lua. So why do I need to manually copy/paste init.lua if I'm just extrating the contents of a zip that could also have the init.lua? I feel like I just got gasslit hehe.

[feoh]

Hi there. I'm very sorry you're having this experience. I know I've been in similar straits many times myself.

First, have you considered contributing? What changes could we make to the README/install to make you less insane?

That said, I'll re-examine the README in hopes of making it clearer.

In any case, yes, the entire file structure must be copied over in its entirety.

You can in fact do this by git cloning right into your ~/.config/nvim, or you can do as I do and clone them somewhere else, reviewing changes as they come down and integrating them into your own dot files as you see fit.

[nPHYN1T3]

One big hurdle for this would be that there is a very popular video that kinda instigates this issue. That would need to be revised heh.

Well for starters if I was to re-write the read me I'd need some input. Like why does the install section gloss over what the video says. i.e. The video says hey just copy the contents of the init.lua and BLAM!? The read me also doesn't really tell you how to do anything. Just kinda says clone the git repo and GLHF.

Then as for the "You must copy the entirety of the kickstart.nvim into your ~/.config/nvim in order for it to work" this is also ambiguous. It doesn't say zip/folder/files. First where do you get those files? First you need to get the zip by clicking on the blue CODE button because there are no release files. Then what? Well then extract the FILES in that archive to your neovim folder ~/.config/nvim. Given the archive has the init.lua what the he11 is the video talking about?! heh.

Cheeky stuff aside it would be a lot clearer if the READ ME had some defined sections. Install via GIT, install via Archive. Hey special note ignore the video we've linked to as it will confuse/complicate things since you NEED to either clone the GIT or download the WHOLE archive.

[feoh]

I have a better idea. Since you feel so strongly about this, why don't YOU make a Youtube video reflecting the current reality instead?

Open source is a gift. That video @tjdevries was another gift. The fact that he gave us that gift some time ago which means it's no longer 100% accurate doesn't mean that we get to be grabby and demand another one.

I'll review the README and see if there's anything further I can add to help this situation. Sorry you had trouble.

[nPHYN1T3]

That would require me to have a google account so no. :P I didn't demand a new video but a disclaimer that a few things might not work in the linked video may help.

I will re-write the install section though so long as you confirm what I say will work.

[feoh]

Can't say I blame you. I have one but I don't love it :) Thanks a bunch I look forward to your pull request!

[nPHYN1T3]

Lol pull request. The primary reason I have an account here was bug reporting. I tried to learn all this git stuff but it does not jive for me. Apparently I'm a living Roger Murtaugh quote.

[feoh]

I'm afraid pull requests are the coin of the realm for open source projects. There are a million billion resources out there to help you understand how to use Github.

[nPHYN1T3]

Sadly I know, I could write it out in here and you could incorporate whatever you wanted but instead I've got to branch and or fork and yada yada. I've read the docs and sadly they also read very much like if you know you'll get it if you don't it will just be a wall of text. You've got to jump around cross referencing things to build the whole picture and cue my Roger Murtaugh joke.

I will perhaps give it another go shortly. Submitted...I think...

[duyminhle95]

import = 'custom.plugins'

thanks so much <3

[diponkumer]

I encountered the same error, after browsing the config for a bit it was an easy fix comment the code on line 189 which says { import = 'custom.plugins' }, This error is produced when there are not already any packages located in lua/custom/plugins. Commenting that line should be an easy fix.

Thanks it works , though it was in 205 number line for me.

[abdelrahman-essawy]

What fixed it for me that, I had to make file

\custom\plugins.lua

and typed inside it :

return {}

[samcdavid]

To fix no specs found for module lazyvim.plugins.extras.editor.symbols-outline I commented out:

{ import = "lazyvim.plugins.extras.editor.symbols-outline" },

in my lua/config/lazy.lua file. After restarting nvim, I didn't get the issue anymore.