Indexing means reading a folder's code and building its graph.

"This folder is not added yet. Run niro init to add it and build it."

niro build only rebuilds folders Niro already knows. Add this one with niro init.

"Two folders were given (<a> and --path <b>). Give one."

You named a folder twice, once directly and once with --path. Give it once.

"This folder is not indexed on this machine. Run niro start here to set it up."

Niro has no graph for this folder. On a computer that is already set up, niro init adds a folder. On a new computer, run niro start.

A file I know exists is missing from every answer.

It may be larger than 2 MB, which is the largest file Niro reads. get_index_status lists files left out for size. Raise the limit with NIRO_LOCAL_MAX_FILE_BYTES, then run niro build. Some answers say only "not found", with no word about the size, so check get_index_status.

A file is listed as one "whose parse passed the 20 s time limit".

A file over 256 KB that takes longer than 20 seconds to read is left out. Raise the limit with NIRO_LOCAL_PARSE_TIMEOUT_SECONDS, then run niro build.

"SKIPPED: N source file(s) larger than 2 MB ... were not indexed"

An answer may be missing something because these files were left out. The line names the first 5 of them, and says how to raise the limits.

Which files and folders does Niro skip?

Niro skips:

Minified or bundled JavaScript shows up as hundreds of methods.

A minified file is code squeezed onto a few lines for shipping. Niro filters many of them out, but one committed to the repository can still be read as code. Add it to .gitignore if it is generated. Mapping it back to its real source is not supported.

Are HTML, Vue and Svelte files read?

Only their script blocks. The page markup itself is not read.

My F#, Visual Basic or PowerShell code is not in the graph.

Niro has no reader for these languages. It counts F# and Visual Basic files in a build's summary, but nothing in them reaches the graph.

Why are my tests in the graph?

Niro reads test code too, so you can see which tests reach a change. Hosted Niro sometimes leaves tests out, so counts can differ between the two.

"another niro-local was writing the graph, and this gave up (it waits at most 120 s ...)"

Two builds ran at once, and the second waited 2 minutes for the first. Run your build again when the first has finished. Raise the wait with NIRO_LOCAL_BUILD_LOCK_WAIT.

A build of a very large repository crashed.

This is a known problem on some very large repositories (a "RecursionError"). Send the error to help@niro.ai.

The watcher's log says "Could not rebuild <folder>: ... Edits are not reaching the graph."

The background rebuild failed. Run niro build in that folder to see the full error. After you fix it, save any file and the watcher tries again.

An answer says "NOTE FROM niro-local: ACTION REQUIRED. The following file(s) were modified after the last index build".

Those files changed after the last build, so the graph may be out of date for them. The answer lists up to 20 of them. Read them directly. The watcher rebuilds them shortly.

An answer says "niro-local is rewriting this folder's code graph right now".

A full build is running. For this one request, search the files (or use code_grep and get_source_code, which keep working), and ask again when the build ends. It does not mean "nothing found".

How long does a build take?

A full build of a repository of about 9,000 files was measured at about 103 seconds. Later rebuilds handle only what changed, and are much quicker.

Does Niro run git, or read my history?

No. It reads three small git files: .git/HEAD (your branch), .git/index (which files git tracks) and .git/config (to tell copies of a repository apart). It never runs git, and never reads your history.

When does the graph update after I save a file?

About 3 seconds after the folder stops changing, if the background watcher is running. Check it with niro status.

A service has the wrong name, or a library shows up as a service.

Niro guesses which folders are separate services from build files and layouts, and sometimes guesses wrong. Two examples:

niro modules shows what it decided. Fixing a wrong guess by hand is not supported yet.

How does Niro find the services in a monorepo?

A monorepo is one repository holding several services. Niro uses each service's build file, and deployment files such as a Docker Compose file, to tell them apart. Some library modules in Cargo, Go, Gradle and .NET are not yet separated out. See Configure a folder.

"the graph at <path> is damaged ... It is rebuilt from what was indexed."

The graph file was damaged, and the engine rebuilds it from its saved build state. Run the command it names.

"the graph was written by an older major version of niro-local; run niro build"

After an upgrade, the graph needs one rebuild in the new format. Run niro build.

"the graph ... was written by a newer major version of niro-local"

A newer Niro wrote this graph, and this older one will not change it. Run niro upgrade.

"The niro-local home ... was last used by a newer niro-local ... Upgrade with: niro upgrade"

Same cause: a newer version used this folder. Run niro upgrade.

When should I use niro build --full?

When you suspect the graph is wrong in a way a normal rebuild does not fix. It reads every file again. A normal rebuild gives the same graph, so you rarely need it.

My folder is in two projects. Which one does niro build build?

Both. Name one with niro build --project <name>.

I deleted a folder. Is its graph still on disk?

Yes, for 14 days after Niro first saw it missing. Then it is removed. To remove it now, run niro clean. If you move the folder back, it is used again.