NX Daemon does not respond after first usage

[foxylion]

Hi, I recently tried out NX and was able to successfully run a command.
Afterwards the daemon does no longer respond. When I tail the logs of the daemon I can see the following:

[NX Daemon Server] - 2024-09-09T14:58:32.556Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.608Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.660Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.712Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.764Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.808Z - [REQUEST]: Updated workspace context based on watched changes, recomputing project graph...
[NX Daemon Server] - 2024-09-09T14:58:32.808Z - [REQUEST]: .nx/workspace-data/d/daemon.log,.nx/workspace-data/storybook.hash,.nx/workspace-data/project-graph.json,.nx/workspace-data/file-map.json,.nx/workspace-data/eslint-7836109672759906007.hash
[NX Daemon Server] - 2024-09-09T14:58:32.808Z - [REQUEST]: .nx/workspace-data/project-graph.json~6d38d8c7,.nx/workspace-data/file-map.json~6d38d8c7,.nx/workspace-data/file-map.json~5e810508,.nx/workspace-data/file-map.json~b7f082c2,.nx/workspace-data/project-graph.json~b7f082c2,.nx/workspace-data/project-graph.json~5e810508
[NX Daemon Server] - 2024-09-09T14:58:32.811Z - Time taken for 'hash changed files from watcher' 3.195973000001686ms
[NX Daemon Server] - 2024-09-09T14:58:32.816Z - [WATCHER]: 0 file(s) created or restored, 2 file(s) modified, 0 file(s) deleted
[NX Daemon Server] - 2024-09-09T14:58:32.868Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.920Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.972Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:33.024Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:33.076Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:33.128Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:33.180Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:33.232Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:33.283Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified

I does this in a endless loop. When I stop the daemon I can run again one command and afterwards it is again in this loop.

Anyone an idea what causes this problem?

My nx.json is pretty simple:

{
  "$schema": "./node_modules/nx/schemas/nx-schema.json",
  "targetDefaults": {
    "build": {
      "outputs": ["{projectRoot}/build"],
      "cache": true
    }
  },
  "defaultBase": "master",
  "plugins": [
    {
      "plugin": "@nx/eslint/plugin",
      "options": {
        "targetName": "lint:eslint"
      }
    },
    {
      "plugin": "@nx/storybook/plugin",
      "options": {
        "serveStorybookTargetName": "storybook:dev",
        "buildStorybookTargetName": "storybook:build"
      }
    }
  ]
}
``

[tlaurie-cl]

I may have found the solution.

If you have the .nx folder in a .gitignore file that is above the root like:
outer/.gitignore
outer/inner/nx.json
outer/inner/.nx/**

Nx appears to not recognize this and actually tracks the files inside of the .nx cache folder. Causing the daemon to infinitely recalculate hashes.

Adding a .gitignore with .nx inside of it into the nx workspace root folder (outer/inner/.gitignore) seems to fix this.

I've created an issue here: #30313