Import can't find files about vscode-motoko HOT 9 OPEN

Thanks for pointing out where I should be looking.

It seems it doesn't like the simlinks my npm setup has and ends in infinite loop. I can fix that on my end.

Edit: Removing looping npm packages fixed it

from vscode-motoko.

It works most of the time. (On Mac/Intel)
However, sometimes I get these errors. (not too often)
reloading VScode or Motoko language server thru palette doesn't help.
I have to close VScode and start it again. Then it works.

from vscode-motoko.

Thanks for the bug report; I'll see if I can reproduce this on my end.

Everything seems alright for a simplified example, so would you be able to send a screenshot of your file / directory structure?

Also, does anything seem unusual in the extension log ("Output" -> "Motoko Language Server")?

The language server is able to handle multiple dfx.json files at a time in any subdirectory, so this is supposed to work even with a different Git root.

from vscode-motoko.

Just to confirm, did this fix the original issue ("sometimes Motoko language server works and finds its files, sometimes it doesn't")?

I'll look into fixing this infinite loop condition to minimize the chance of the same situation happening in the future.

from vscode-motoko.

That is quite strange. What operating system are you using?

This might have something to do with VS Code itself rather than the extension, since the error messages indicate that the system path doesn't include npx or mops while the extension is being initialized.

from vscode-motoko.

MacOs 13.4

from vscode-motoko.

Thanks! I'll let you know if I find a way to reproduce this issue on my end (also on macOS 13.4).

You could try running mops sources and npx ic-mops sources in a terminal to see if anything unexpected happens (and then running code . from the same terminal to inherit the system path). If this doesn't help, then it might be worth reinstalling VS Code and perhaps running the Motoko extension by itself to try and narrow down the root cause.

from vscode-motoko.

Hi @infu, are you still running into this issue? Here are a few more debugging steps that might help narrow down what's happening:

• What happens if you remove or change defaults.build.packtool in your dfx.json file?
• Do you get a "command not found" message when running which npx and which mops in the VS Code dev console?

from vscode-motoko.

same issue here

from vscode-motoko.