chore: walk up from cwd to find .env#21
Merged
Merged
Conversation
Devs run \`mirrorstack\` from many places inside the workspace — the meta-repo root, a module subdirectory, a scaffold target. The previous \`dotenvy::dotenv()\` only checked cwd, so workspace-level .env files at \`MirrorStack-AI-V2/.env\` or \`mirrorstack-cli/.env\` were silently missed when invoked from sibling dirs. This walks from cwd upward to the filesystem root and loads the first .env it finds. Process env vars still take precedence (dotenvy's default is non-overriding), so per-invocation \`MIRRORSTACK_API_URL=...\` still works. Silently ignored when no .env exists anywhere on the path (the common case for installed users). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces the cwd-only `dotenvy::dotenv()` with an upward search from cwd to the filesystem root. The first `.env` found gets loaded.
Why
Devs run `mirrorstack` from many places inside the workspace:
Previously, only the `.env` directly in cwd loaded — so a workspace `.env` at `MirrorStack-AI-V2/.env` was silently missed when running from a module subdirectory. Users hit this when login URLs pointed at production while their `.env` had localhost overrides.
Behavior
Test plan
🤖 Generated with Claude Code