E013: Imported File Not Analyzed

Severity: Hint

imported file `./utils.nix` has not been analyzed -- add it to [project] analyze in
tix.toml or open it in the editor

An import ./path.nix resolved to a real file, but that file hasn’t been type-checked yet. The imported value’s type is unconstrained (?). This is a hint, not a warning – it’s normal in unconfigured projects.

When does this appear?

In most cases, the LSP resolves imports automatically: when you open a file that imports another, the imported file is inferred from disk on demand. E013 only appears when demand-driven inference fails or is unavailable – for example, if the imported file has a parse error that prevents inference.

Common causes

• The imported file has syntax errors that prevent parsing.
• The import target is generated or doesn’t exist on disk yet.

How to fix

• Fix any syntax errors in the imported file.
• If the file is generated, add it to the analyze list so it’s pre-analyzed:

  [project]
  analyze = ["lib/*.nix", "utils/*.nix"]
  

• Or open the imported file in your editor – the LSP will analyze it and re-check dependents automatically.