You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I use nix flakes and I cannot use more than one shell because devenv now "temporarily" requires adding devenv-up = self.devShells.${system}.default.config.procfileScript; attribute to packages. I know I can replace default with any other shell but it breaks any composability.
To reproduce
Spin up a devenv using the fake setup from the example and try to add another devshell.
Version
1.0.4 with flakes
The text was updated successfully, but these errors were encountered:
The UX around this is not great, but here's how to create multiple shells with plain flakes:
# Assuming flake-utils here to skip setting system{packages={# The "default" shelldevenv-up=self.devShells.${system}.default.config.procfileScript;# Another shell. The pattern is: <shellName>-devenv-upcross-devenv-up=self.devShells.${system}.cross.config.procfileScript;};devShells={default=devenv.lib.mkShell{ ... };cross=devenv.lib.mkShell{ ... };};}
If you're using flake-parts, the devenv-up packages are created for you.
Describe the bug
I use nix flakes and I cannot use more than one shell because devenv now "temporarily" requires adding
devenv-up = self.devShells.${system}.default.config.procfileScript;
attribute to packages. I know I can replacedefault
with any other shell but it breaks any composability.To reproduce
Spin up a devenv using the fake setup from the example and try to add another devshell.
Version
1.0.4 with flakes
The text was updated successfully, but these errors were encountered: