-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
--watch-path doesn't run the JavaScript file #47296
Comments
I think we can mark this confirmed bug too? I am trying to take a shot at this |
Ran into this issue as well when executing From what I'm seeing, Addendum:
|
I think the problem lies of over here node/lib/internal/main/watch_mode.js Line 53 in 85705a4
its possible i think when watch mode is running with --watch-path the child process is not connected to the parent process and hence the console logs are lost? not sure though what exactly could be the right options it seems passing cc @MoLow |
PR-URL: #47369 Fixes: #47296 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
PR-URL: #47369 Fixes: #47296 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
PR-URL: #47369 Fixes: #47296 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
PR-URL: #47369 Fixes: #47296 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
PR-URL: #47369 Fixes: #47296 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
PR-URL: #47369 Fixes: #47296 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
PR-URL: #47369 Fixes: #47296 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
PR-URL: #47369 Fixes: #47296 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
PR-URL: nodejs#47369 Fixes: nodejs#47296 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
Version
v19.8.1
Platform
Darwin [redacted] 22.3.0 Darwin Kernel Version 22.3.0: Mon Jan 30 20:39:35 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T8103 arm64
Subsystem
command line options?
What steps will reproduce the bug?
With this file as
index.js
:Run any of the following commands:
How often does it reproduce? Is there a required condition?
Every time
What is the expected behavior? Why is that the expected behavior?
I would expect the index.js file to run and "hello" be printed to the screen every time the file changes.
What do you see instead?
I see the messages of
Restarting index.js
, but nohello
.Additional information
No response
The text was updated successfully, but these errors were encountered: