-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(core): read socket dir on demand & load .env files on client startup #23348
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 2b68353. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
83ee805
to
2b68353
Compare
…tup (#23348) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> ## Current Behavior The daemon doesn't correctly read the `NX_DAEMON_SOCKET_DIR` env variable if it's set in `.env`. Also, the `.env` files aren't loaded if the daemon client is imported & used directly (like it is in Nx Console). ## Expected Behavior The daemon should correctly read the `NX_DAEMON_SOCKET_DIR` variable regardless of where it's specified and setting it shouldn't cause any issues with Nx Console. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes nrwl/nx-console#2114 (cherry picked from commit 6c36bef)
…tup (#23348) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> ## Current Behavior The daemon doesn't correctly read the `NX_DAEMON_SOCKET_DIR` env variable if it's set in `.env`. Also, the `.env` files aren't loaded if the daemon client is imported & used directly (like it is in Nx Console). ## Expected Behavior The daemon should correctly read the `NX_DAEMON_SOCKET_DIR` variable regardless of where it's specified and setting it shouldn't cause any issues with Nx Console. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes nrwl/nx-console#2114
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
The daemon doesn't correctly read the
NX_DAEMON_SOCKET_DIR
env variable if it's set in.env
.Also, the
.env
files aren't loaded if the daemon client is imported & used directly (like it is in Nx Console).Expected Behavior
The daemon should correctly read the
NX_DAEMON_SOCKET_DIR
variable regardless of where it's specified and setting it shouldn't cause any issues with Nx Console.Related Issue(s)
Fixes nrwl/nx-console#2114