Question 1

How do I use niv with a private GitHub repo?

Accepted Answer

You can use the git protocol with SSH keys or set up a .netrc file with your GitHub token, then configure Nix to use it, as detailed in the FAQ section on private repositories.

Question 2

niv vs Nix flakes: which is better for dependency management?

Accepted Answer

niv is a simpler, file-based tool that works well with existing Nix workflows, while flakes offer a more integrated, modern approach with better reproducibility; choose niv if you value minimalism and compatibility with older setups.

Question 3

How to update all dependencies at once with niv?

Accepted Answer

Run 'niv update' without arguments to update all packages in nix/sources.json to their latest versions based on configured branches or templates, as shown in the update command examples.

Question 4

Can niv handle git dependencies with submodules?

Accepted Answer

Yes, but you need to manually add 'submodules': true to the dependency in sources.json after adding it with the git command, as explained in the FAQ on submodules.

Question 5

How do I override a dependency with a local path in niv?

Accepted Answer

Set an environment variable like NIV_OVERRIDE_<name> to the local path, and niv will use that instead of the remote source, useful for development, as described in the local packages FAQ.

Question 6

What's the difference between niv add and niv update?

Accepted Answer

'niv add' inserts a new dependency into sources.json, while 'niv update' modifies an existing one, such as changing its version or branch, and can update all packages at once.

Question 7

How to import a NixOS module using niv?

Accepted Answer

After adding the package with niv, import it in your Nix configuration using the source path, like (sources.package + '/path/to/module'), as shown in the FAQ on importing NixOS modules.

niv

What is niv?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions