Module not found

[bfren]

Setup

• Windows 11 Pro
• Nushell 0.111.0
• VSCodium 1.110.11631
• Nushell extension 2.0.4 (same behaviour on this and the release version)

Environment

I have a suite of Docker images containing Nu scripts, grouped into modules.

In the VSCodium workspace config I have various 'nushellLanguageServer.includeDirs' defined to import modules into the source for each Docker image.

Error

Switching on today to update one of my images I noticed the following:

The files / modules all exist and have correct mod.nu etc, and the image runs fine, so I am assuming this is an issue with the extension? I have switched trace on in the extension settings and don't see anything useful in there. It feels like the include directories are no longer being included by the extension / LSP?

Unfortunately both Nushell and VSCodium have had updates since I last worked on the project.

[fdncred]

It depends on which extension you're running. IIRC the Include Dirs section of the extension config is for the Release version of the extension. I don't believe it works with the Pre-Release version of the extension. The Pre-Release version uses the extension uses the built-in LSP and by-passes these settings. I remember seeing people having a lsp.nu to enable settings like NU_LIB_DIRS but that was in neovim.

I think the ideal solution would be to allow the lsp to start like this: nu --config lsp.nu --lsp and then, assuming lsp.nu is in a known folder accessible by nu, one would put any startup files/vars/custom commands/aliases/NU_LIB_DIRS/etc in lsp.nu and it would be sourced and in scope when the lsp starts. I'd love to see a PR for this functionality.

[bfren]

OK I'll give that a go - I was having the issue with the Release version though - I tried the Pre-release in case something had been fixed.

[fdncred]

Interesting. I'm actually not having any issues with the Pre-Release version. It's been a while since I looked at the code so I'm not sure how it's finding these. I guess it has to be with the include dirs setting but, like i said, i thought that was ignored in pre-release. I can click on these and then "Go to Definition" and everything works fine.

[bfren]

Yes that was my previous experience / behaviour. I'll do some more digging and see if I can work out what changed that caused the break.

[fdncred]

oh, I think it's because I have the scripts in a default folder. So, if I start nushell with nu -n and then do $env.NU_LIB_DIRS it's prepopulated with 2 folders. In one of those folders is where all the stuff lives above. So, I think that's why it just works for me. If I had another folder that isn't in the default setup, I'd probably have problems.

[fdncred]

You can also enable the output window with Nushell LSP Trace

Or Nushell Language Server to see some debug messages. I'm not sure if both are used or not.

[bfren]

hmmm, I've tried setting $NU_LIB_DIRS in env.nu - but I got confused reading issues / online stuff about that vs $env.NU_LIB_DIRS to know which does what and why. It feels like any modules found in those paths should be loaded at startup but that doesn't appear to happen. When I put something in the default location - as you have - then I can load my modules.

I just can't work out what's changed to stop this working! The trace output contains a whole bunch of stuff but nothing helpful as far as I can tell regarding module imports.

[bfren]

Think I've cracked it! Found this and shadowed the const in my env.nu with the locations of my modules, restarted the LSP and I have my modules back!

[fdncred]

Did you do what I said nu --config lsp.nu --lsp? I believe when the lsp starts, no files are loaded so changing the env.nu won't make any difference. It's like launching nushell with nu -n, no config file, no env file, no nothing. There's documentation in the book that specifically says what files are loaded and when they're loaded but it has no info about lsp.

[bfren]

No - in my default env.nu file I added

$NU_LIB_DIRS = $NU_LIB_DIRS ++ [
 ...
]

So the LSP does appear to load env.nu. I've got full code completion back, with arg hinting and everything.

> nu -n
> $nu.env-path
C:\Users\Ben\AppData\Roaming\nushell\env.nu

I put it in there.

[fdncred]

nice. glad you figured it out. if you do nu --log-level info --lsp you can see exactly what's going on. sorry it took a while for me to remember this. It looks to me like it loads plugins, env.nu, config.nu, then the vendor autoload dirs.

[bfren]

... that said, I still don't actually know why it broke, just how to fix it!!

[bfren]

Ok so this is curious... I have two dev environments. One is Windows 11 which was fixed according to the above. The other is macOS - and on that, exactly the same config file but with different paths to match the filesystem there - and use xxx gives me the 'module not found' error. Doing ls on all $NU_LIB_DIRS entries lists everything correctly. Same thing happens on WSL.

Something v weird going on here. I went on just now to copy the config across so I can do some dev work on my laptop - all still working beautifully with LSP on my PC.