Add `__NIX_DARWIN_SET_ENVIRONMENT_DONE` to default pass through envs (`globalPassThroughEnv`) about turbo HOT 8 CLOSED

Ah, I see. Yes, that'd certainly be interesting but not sure if we would roadmap it as it stands. This has been the first ask for this that I've heard!

from turbo.

Hey, thanks for the issue!

In the interest of being somewhat judicious about what we add to that list, I'd like to learn if this is a highly common use case in NixOS. I'm looking at their environment variables list and don't see the variable you're referring to. Is this something every NixOS user needs?

from turbo.

Thanks for the quick reply!

If I'm honest, I'm not too sure about the specifics. I only discovered this environment variable after hours of debugging why my $PATH was wrong inside child shells.

I imagine it's not listed there because it's an implementation detail—it's not something you're supposed to set yourself, rather it's set for you. I believe the issue only occurs when a tool like Turborepo prevents this environment variable from being passed down to a child shell.

cc my co-worker @samhh who may know better

from turbo.

It comes from nix-darwin, not NixOS proper. This is the most relevant reference in the repo: https://github.com/LnL7/nix-darwin/blob/fabc653517106127e2ed435fb52e7e8854354428/modules/environment/default.nix#L195

I'd guess a significant minority of macOS Nix users use nix-darwin, and all of these will require this fix for subshells under Turbo.

from turbo.

That being the case, I'd recommend adding that variable to your repo's passthroughs. Alternatively, you could use Loose Mode for that invocation if you're still having trouble.

Our (admittedly non-scientific) criteria for adding to the default passthroughs is to capture the most vastly common, baseline cases for the most frequently used tools, so this case doesn't sound like it fits. In my thinking, the NIX_* namespace would be something we'd add but not __NIX_*.

Does that make sense? Hoping I explained that well enough and it tracks with the way NixOS works from what I'm gathering from your info here.

from turbo.

That's fair. We're successfully using a global passthrough now absent an upstream solution. Maybe you could reconsider in the future if lots of other users hit the same issue, or if it never reaches critical mass at least it's documented here now.

My only qualm is that this feels similar to the anti-pattern of placing per-user configuration in per-repo VCS ignore files, but it'd be non-trivial to solve; I don't think Turbo has a global per-user config yet?

from turbo.

Going to close here given the above commentary.

@samhh, I'm interested, though. What do you mean by "global per-user config"?

from turbo.

What do you mean by "global per-user config"?

Something like ~/.config/turbo/config.json. Global passthroughs there would be analogous to global VCS ignores in ~/.config/git/ignore.

from turbo.