We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When this package is used, we can't exit node --inspect[-*] debug server with ctrl-C, or kill it with SIGTERM. This is due to tapjs/signal-exit#71.
node --inspect[-*]
1$ # terminal 1: debug server 1$ cat index.js # very simple script console.log("a"); 1$ node --inspect-brk index.js 2$ # terminal 2: debug client 2$ node inspect --port=9229 connecting to 127.0.0.1:9229 ... ok Break on start in index.js:1 > 1 console.log("a"); 2 debug> # terminal1 Debugger attached. ^C 1$ # killed with Ctrl-C
When proper-lockfile is used:
1$ cat index.js const lockfile = require("proper-lockfile"); console.log("a"); 1$ node --inspect-brk index.js 2$ node inspect --port=9229 connecting to 127.0.0.1:9229 ... ok Break on start in index.js:1 > 1 const lockfile = require("proper-lockfile"); 2 console.log("a"); 3 debug> n break in index.js:2 1 const lockfile = require("proper-lockfile"); > 2 console.log("a"); 3 # now we can't kill the server! # terminal1 Debugger attached. ^C^C^C^C^C
Tested environment:
The text was updated successfully, but these errors were encountered:
I think we should wait for tapjs/signal-exit#71 to be responded in the meantime.
Sorry, something went wrong.
No branches or pull requests
When this package is used, we can't exit
node --inspect[-*]
debug server with ctrl-C, or kill it with SIGTERM. This is due to tapjs/signal-exit#71.When proper-lockfile is used:
Tested environment:
The text was updated successfully, but these errors were encountered: