Warning: This program is experimental and its interface is subject to change.
nix develop - run a bash shell that provides the build environment of a derivation
nix develop [option...] installable
Start a shell with the build environment of the default package of the flake in the current directory:
# nix develop
Typical commands to run inside this shell are:
# configurePhase # buildPhase # installPhase
Alternatively, you can run whatever build tools your project uses directly, e.g. for a typical Unix project:
# ./configure --prefix=$out # make # make install
Run a particular build phase directly:
# nix develop --unpack # nix develop --configure # nix develop --build # nix develop --check # nix develop --install # nix develop --installcheck
Start a shell with the build environment of GNU Hello:
# nix develop nixpkgs#hello
Record a build environment in a profile:
# nix develop --profile /tmp/my-build-env nixpkgs#hello
Use a build environment previously recorded in a profile:
# nix develop /tmp/my-build-env
Replace all occurrences of the store path corresponding to
glibc.devwith a writable directory:
# nix develop --redirect nixpkgs#glibc.dev ~/my-glibc/outputs/dev
Note that this is useful if you're running a
nix developshell for
~/my-glibcand want to compile another package against it.
nix develop starts a
bash shell that provides an interactive build
environment nearly identical to what Nix would use to build
installable. Inside this shell, environment variables and shell
functions are set up so that you can interactively and incrementally
build your package.
Nix determines the build environment by building a modified version of
the derivation installable that just records the environment
stdenv and exits. This build environment can be
recorded into a profile using
The prompt used by the
bash shell can be customised by setting the
bash-prompt-suffix settings in
nix.conf or in the flake's
If no flake output attribute is given,
nix develop tries the following
flake output attributes:
If a flake output name is given,
nix develop tries the following flake
Instead of starting an interactive shell, start the specified command and arguments.
start an interactive environment if evaluation fails
Clear the entire environment (except those specified with
Keep the environment variable name.
The stdenv phase to run (e.g.
The profile to update.
Redirect a store path to a mutable location.
Unset the environment variable name.
Common evaluation options:
Pass the value expr as the argument name to Nix functions.
Pass the string string as the argument name to Nix functions.
The Nix store to use for evaluations.
Allow access to mutable paths and repositories.
Add path to the list of locations used to look up
Override the flake registries, redirecting original-ref to resolved-ref.
Common flake-related options:
Commit changes to the flake's lock file.
Use the inputs of the specified flake as registry entries.
Don't allow lookups in the flake registries. This option is deprecated; use
Do not allow any updates to the flake's lock file.
Do not write the flake's newly generated lock file.
Override a specific flake input (e.g.
dwarffs/nixpkgs). This implies
Recreate the flake's lock file from scratch.
Update a specific flake input (ignoring its previous entry in the lock file).
Options that change the interpretation of installables:
Operate on the store derivation rather than its outputs.
Interpret installables as attribute paths relative to the Nix expression expr.
Interpret installables as attribute paths relative to the Nix expression stored in file. If file is the character -, then a Nix expression will be read from standard input. Implies