Skip to content
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

nx debug fails to start with a weird console message: ^[[7;1R #2179

Closed
kalvintamas opened this issue Jun 21, 2024 · 1 comment
Closed

nx debug fails to start with a weird console message: ^[[7;1R #2179

kalvintamas opened this issue Jun 21, 2024 · 1 comment
Labels
type: bug Something isn't working

Comments

@kalvintamas
Copy link

Current Behavior

When running nx serve run configuration, the above message is printed to the console, and the app doesn't start.

Expected Behavior

Expected to run.

Steps to Reproduce

I don't really know how to reproduce this. This bug just appears sometimes (ca. 20% of start attempts), and sometimes it doesn't.

I downloaded nx-examples and after some struggle, I could start it, I tried it a few times, but since I don't know what triggers this, I couldn't really do much.
This project is a company project I would not share public, but I collected IntelliJ logs, I hope they help.

Failure Logs / Images / Videos

<project_path>\node_modules\.bin\nx.cmd run bdpst-fs-frontend:serve
Debugger listening on ws://127.0.0.1:57319/8319f305-8d38-436c-acc8-c43edea67b30
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.

> nx run bdpst-fs-frontend:serve:development

^[[7;1R

I also collected IntelliJ logs that I attached.
idea.log

Environment

Node   : 20.11.1
OS     : win32-x64
npm    : 10.2.4

nx (global)        : 19.1.0
nx                 : 18.1.3
@nx/js             : 18.3.4
@nx/jest           : 18.1.3
@nx/linter         : 18.1.3
@nx/eslint         : 18.1.3
@nx/workspace      : 18.1.3
@nx/angular        : 18.3.4
@nx/cypress        : 18.1.3
@nx/devkit         : 18.3.4
@nx/eslint-plugin  : 18.1.3
@nrwl/tao          : 18.1.3
@nx/web            : 18.1.3
@nx/webpack        : 18.3.4
typescript         : 5.3.2
---------------------------------------
Community plugins:
@ngrx/component         : 17.2.0
@ngrx/component-store   : 17.2.0
@ngrx/effects           : 17.2.0
@ngrx/eslint-plugin     : 17.2.0
@ngrx/operators         : 17.2.0
@ngrx/router-store      : 17.2.0
@ngrx/store             : 17.2.0
@ngrx/store-devtools    : 17.2.0
ngrx-immer              : 2.2.0
ngx-extended-pdf-viewer : 19.7.1
ngx-spinner             : 16.0.2
ngx-toastr              : 17.0.2
---------------------------------------
The following packages should match the installed version of nx
  - @nx/[email protected]
  - @nrwl/[email protected]
  - @nx/[email protected]
  - @nrwl/[email protected]
  - @nx/[email protected]
  - @nrwl/[email protected]
  - @nx/[email protected]
  - @nrwl/[email protected]

To fix this, run `nx migrate [email protected]`
  • Nx Console version: 1.26.0
  • IntelliJ version: 2024.1.3 (Ultimate)
@kalvintamas kalvintamas added the type: bug Something isn't working label Jun 21, 2024
@MaxKless
Copy link
Collaborator

Hey thanks for the report!
This is very likely a duplicate of nrwl/nx#22358

We're still working on a proper fix for this but for now you can set
NX_NATIVE_COMMAND_RUNNER=false in your root .env file as a workaround.

I'll close this as a duplicate but let me know if you run into any other issues :)

@MaxKless MaxKless closed this as not planned Won't fix, can't repro, duplicate, stale Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants