Ross A. BakerOct 8, 2025

New project to share and compose Nix devshells:

https://codeberg.org/rossabaker/shell-game/

I'm a fan of Numtide's devshells, but have struggled to fold my ad hoc definitions for unflaked projects into published devshells for my projects with flakes. This fixes it for me.

#Nix #Devshells #ShellGame

shell-game

Generic nix devshells for playing around

Codeberg.org
adingbatponder  👾Aug 12, 2025
🚀 #NixOS + #Rust + #flakes + #devshells .
Video shows using Rust on NixOS, taking full advantage of flakes & devshells to make packaging programs for NixOS easier.
Nice for dealing with #nixpkgs / #nixospackages .
🎥 https://youtu.be/Ss1IXtYnpsg
#Linux #DevTools
#vimjoyer
Bit RegurgitatorMay 30, 2025

Find why your devShell, package, etc depends on something interactively!

`nix-tree --derivation .#devShells.x86_64-linux.default`

https://github.com/utdemir/nix-tree

#Nix #NixFlakes #NixOS

GitHub - utdemir/nix-tree: Interactively browse dependency graphs of Nix derivations.

Interactively browse dependency graphs of Nix derivations. - utdemir/nix-tree

GitHub
Sam Lehman Apr 8, 2025

A big shortcoming of #Nix #devshells is that it's difficult to wrap #editor & #LSP configs for your project.

This is the number one thing I would want a #devshell for after installing dependencies, rendering them always inadequate/incomplete.

Show threadsystemd-jaded.timerJan 27, 2024

@terrorjack (the creativity necessary to use a nix file is essentially `nix eval --json .#devShells.x86_64-linux.devShells.default --apply 'builtins.unsafeGetAttrPos "buildInputs"'`, shoving that position into your choice of nix parser such as rnix, then finding any list that's unconditionally added there and adding it)

(it's not *hard*, i just don't think anyone with the necessary knowledge has actually done it because they simply have other stuff to do)

LinusJan 26, 2024
@tristanC I'm not sure there's a tool for doing exactly what you're asking for yet (but it would be really nice to have and shouldn't be too hard to implement!), but nix-diff could be interesting for observing the changes in what you end up building. Apply nix-diff to the shell drv files before and after (nix eval .#devShells.x86_64-linux.default.drvPath) and it'll show you exactly what changed on the derivation level — so what's actually built.