NX does not restart the project in "serve" mode

[amir-khoshbakht]

Current Behavior

there is integrated monorepo with only one nestjs app in it. if I make a file that is syntactically incorrect. for exmple :

exportttt class ServeTest {

}

in that it will detect the change and will restart the app and will show this error: but in the next change even if I correct the problem it will say:

Expected Behavior

The server must be restarted in any case with the new changes

GitHub Repo

No response

Steps to Reproduce

1. npx create-nx-workspace@latest serve-test --pm=yarn
2. Create a file in path: " serve-test/apps/serve-test" with content similar to this:

exportttt class ServeTest {

}

3. run the app: yarn nx run serve-test:serve

Note: This problem does not exist on the same system in a project with Nx version 15.9.2

Nx Report

Node   : 18.16.0
   OS     : win32 x64
   yarn   : 1.22.19
   Hasher : Native

   nx (global)        : 16.2.2
   nx                 : 16.2.2
   @nx/js             : 16.2.2
   @nx/jest           : 16.2.2
   @nx/linter         : 16.2.2
   @nx/workspace      : 16.2.2
   @nx/devkit         : 16.2.2
   @nx/eslint-plugin  : 16.2.2
   @nx/nest           : 16.2.2
   @nx/node           : 16.2.2
   @nrwl/tao          : 16.2.2
   @nx/webpack        : 16.2.2
   typescript         : 5.0.4

Failure Logs

No response

Operating System

• [ ] macOS
• [ ] Linux
• [X] Windows
• [ ] Other (Please specify)

Additional Information

No response

[JonWallsten]

I have the same issue. Whenever there's an error in some remote or library it terminatates the build:

It's obviously really annorying. Let me know if you need any debug information.

[Filoz]

Hi, I have the same problem on windows

[github-actions[bot]]

This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. If we missed this issue please reply to keep it active. Thanks for being a part of the Nx community! 🙏

[github-actions[bot]]

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.