Undeclared identifiers in .nims files

[marcinczenko]

Nim version: 2.0.8 [MacOSX: arm64]
VSCode Extension Version: v0.9.0

I am quite new to Nim ecosystem and community. I am using vscode-nim extension and when writing Nim Script files .nims, I am getting lots of undeclared identifier errors. For example:

mode = ScriptMode.Verbose

task hello, "say hello":
  echo "Hello, world!"

When running nim check on that file everything is working fine and no problems are reported, which seemed to be a problem in the past as well (see nim-lang/Nim#19440).

Is there a way to fix this? Or maybe at least a way to ignore certain (type of) file?

[Anuken]

I am encountering similar issues.

I have no experience with VSC extensions, but removing .nims from the list of extensions might help as a temporary measure?

[NitroPlum]

This is also happening for me on Windows 11. Is there any update on a fix for this?

[xrfez]

I imported system/nimscript to try and force something and it cleared the errors. I removed the import line because you really should never import system. Afterwards it seems like the errors were cleared and not coming back. Spooky.

Along these lines the base config.nims from nimble init, nimble setup calls system.fileExists() and reads like it is ambiguous/undeclared. Calling without the system namespace clears up the error but I do not know what that could break:

# begin Nimble config (version 2)
when withDir(thisDir(), fileExists("nimble.paths")):  # Do not use system.fileExists()
  include "nimble.paths"