## The problem
Issue nrwl/nx#17070 (closed, 83 comments): After upgrading to Nx 16.2.1, the @nx/js:node dev server gets stuck printing "> NX File change detected. Restarting..." in a loop and never actually serves. Downgrading to 16.1.4 avoids it, so it is a regression in the 16.2 line.

## What fixed it
Fixed upstream in Nx 16.5.3, per maintainer jaysoo (the fix shipped via PR #18145). If your @nx/js:node dev server spins on "File change detected. Restarting..." after a 16.x upgrade, upgrade to 16.5.3 or newer rather than pinning to 16.1.4. The restart loop was a watcher bug in the node executor, not a problem with your file setup.