Watch mode for node package executor exits immediately

[DibyodyutiMondal]

Current Behavior

Running the @nrwl/node:package executor in watch mode exits immediately after the initial compilation
Looking to update the dependencies, I ran npx nx migrate @nrwl/workspace
This updated @nrwl/node as well, and then the build target with watch mode stopped working as it used to

9:28:36 am - Starting compilation in watch mode...


9:28:38 am - Found 0 errors. Watching for file changes.
Copying asset files...   
Done copying asset files.
PS my/workspace/path>       <== the command has exited immediately

Expected Behavior

The command should not exit and continue watching for changes
I ran npx nx migrate @nrwl/node@11.4.0 (the version I was on before I ran the workspace update) and the problem disappeared
@nrwl/workspace and other nrwl libraries are still at v11.6.1

9:35:57 am - Starting compilation in watch mode...


9:35:59 am - Found 0 errors. Watching for file changes.
Copying asset files...   
Done copying asset files.         <=== the command continues

Environment

Node : 14.16.0
OS : win32 x64
npm : 6.14.11

nx : Not Found
@nrwl/angular : 11.6.1
@nrwl/cli : 11.6.1
@nrwl/cypress : 11.6.1
@nrwl/devkit : 11.6.1
@nrwl/eslint-plugin-nx : 11.6.1
@nrwl/express : Not Found
@nrwl/jest : 11.6.1
@nrwl/linter : 11.6.1
@nrwl/nest : Not Found
@nrwl/next : Not Found
@nrwl/node : 11.6.1
@nrwl/react : Not Found
@nrwl/schematics : Not Found
@nrwl/tao : 11.6.1
@nrwl/web : Not Found
@nrwl/workspace : 11.6.1
@nrwl/storybook : Not Found
@nrwl/gatsby : Not Found
typescript : 4.1.5

[DibyodyutiMondal]

This still exists in @nrwl/node 12.0.6

In fact, if @nrwl/workspace is as v12, then even rolling back @nrwl/node to v11 does not work, as it did previously

EDIT: It works as long as @nrwl/node is at 11.4.0 (I was mistakenly trying 11.6.1)

[DibyodyutiMondal]

Can confirm it works using @nrwl/node@12.3.4

Thank you, nrwl! You are amazing!

[github-actions]

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.