Running nx build on node project never starts, prints ^[[13;1R

[mayhew3]

Current Behavior

When I run nx build on a node project, I get the following output:

> nx build taskmaster-node


 NX   Took longer than 3 seconds to hear from heartbeat process

The heartbeat process may have not started properly. This CIPE could have inconsistent status reporting.


> nx run taskmaster-node:build

^[[13;1R

And nothing else happens, so I have to kill the process. Strangely, this happens about 75% of the time I try to build. So I usually have to try 3-4 times before it actually kicks off and completes successfully. I don't know even how to start debugging this, since there is no error behind reported.

I have 5 node projects in my monorepo, and this behavior is the same with all of them.

Expected Behavior

I expect the project to build.

GitHub Repo

https://github.com/mayhew3/mm-projects-nv

Steps to Reproduce

1. Run nx run mm-project-nv:build:production or mm-project-nv:serve:development

This was just a project created with create-nx-workspace, and running either of these commands hangs around 75% of the time with the same gobbledeegook.

Nx Report

NX   Report complete - copy this into the issue template

Node   : 20.12.0
OS     : win32-x64
npm    : 10.5.1

nx (global)        : 18.2.2
nx                 : 18.2.2
@nx/js             : 18.2.2
@nx/jest           : 18.2.2
@nx/linter         : 18.2.2
@nx/eslint         : 18.2.2
@nx/workspace      : 18.2.2
@nx/angular        : 18.2.2
@nx/cypress        : 18.2.2
@nx/devkit         : 18.2.2
@nx/eslint-plugin  : 18.2.2
@nrwl/tao          : 18.2.2
@nx/web            : 18.2.2
@nx/webpack        : 18.2.2
typescript         : 5.4.5

Failure Logs

No response

Package Manager Version

No response

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

No response

[mkhodan]

@mayhew3 I'm facing the same issue but what I found is that it's actually waiting for user input for some reason. If I just press Enter it proceeds to executing nx command(It usually reproduces for me when running serve or e2e).

[mayhew3]

Weird, yeah, that works for me, though I never would have guessed! Still seems like a bug, since there is no text asking for input, but at least I can get past it now.