Closed SuneRadich closed 3 months ago
Update: It seems to be tied to the Node version I am running (18.17.1). If I update to Node to latest LTS (20.12.2) then the problem goes away.
So my guess is, that this is somehow tied to Node 18, and some update on OSX.
Same issue on node 20.11.1
Upgrading to 20.12.2
fixed it
I can confirm that with 20.12.2
the issue is finally gone! This was VERY annoying.
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
Current Behavior
If I have an nxCloudAccessToken in my nx.json file, I am unable to stop
nx serve
andnx build
commands using CTRL-C in a terminal. This happens both in VS Code, and in the default OSX Terminal app. It has been working fine in the past. As far as I can recall, it worked fine last week.If I remove
"nxCloudAccessToken": "XXXXX"
from nx.json, things work as expected, and I am able to stop my serve command.It seems that if nx tries to use the distributed cache, the terminal is affected in some way.
The git repo I link in this issue is a brand new nx 17.3.1 repo, and the repo contains a single branch with the only change being that I ran
nx connect
. The main branch works fine, the withToken branch does not.When running
nx serve test
on the withToken branch I can see ^D being shown in the terminal, this is not shown in the main branch. See the two videos below:https://github.com/nrwl/nx/assets/1249306/a9f498ac-2941-418a-be5b-936cfbd1fbc2
https://github.com/nrwl/nx/assets/1249306/860253d1-4dbc-4947-b823-8490471e7006
Expected Behavior
I expect to be able to stop
nx serve
ornx build
by issuing CTRL-C, and not having to kill the entire terminal.GitHub Repo
https://github.com/SuneRadich/nx-token-issue
Steps to Reproduce
npx create-nx-workspace@17.3.1
(naming the repo and app test)nx connect
nx serve test
Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
At work, we have experienced this on at least three different Macbooks, but the issue does not seem to hit Windows 11 users.