Debugging npm scripts without modifying package.json
up vote
0
down vote
favorite
Is there any way to put $NODE_DEBUG_OPTION in the WebStorm run/debug config rather than rewrite the package.json script command to explicitly run node?
webstorm
edited Nov 19 at 19:32
LazyOne
105k20239256
asked Nov 19 at 16:00
Kevin
1,497197
add a comment |
up vote
0
down vote
favorite
Is there any way to put $NODE_DEBUG_OPTION in the WebStorm run/debug config rather than rewrite the package.json script command to explicitly run node?
webstorm
edited Nov 19 at 19:32
LazyOne
105k20239256
asked Nov 19 at 16:00
Kevin
1,497197
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Is there any way to put $NODE_DEBUG_OPTION in the WebStorm run/debug config rather than rewrite the package.json script command to explicitly run node?
webstorm
edited Nov 19 at 19:32
LazyOne
105k20239256
asked Nov 19 at 16:00
Kevin
1,497197
Is there any way to put $NODE_DEBUG_OPTION in the WebStorm run/debug config rather than rewrite the package.json script command to explicitly run node?
webstorm
webstorm
edited Nov 19 at 19:32
LazyOne
105k20239256
asked Nov 19 at 16:00
Kevin
1,497197
edited Nov 19 at 19:32
LazyOne
105k20239256
asked Nov 19 at 16:00
Kevin
1,497197
edited Nov 19 at 19:32
LazyOne
105k20239256
edited Nov 19 at 19:32
LazyOne
105k20239256
edited Nov 19 at 19:32
LazyOne
105k20239256
105k20239256
asked Nov 19 at 16:00
Kevin
1,497197
asked Nov 19 at 16:00
Kevin
1,497197
asked Nov 19 at 16:00
Kevin
1,497197
1,497197
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
No; adding $NODE_DEBUG_OPTION to package.json manually is the only way to debug the application started via npm script, because you have to make sure that Node.js process you'd like to debug is started with appropriate debug options (--debug-brk, --inspect-brk, etc), and the IDE can't control the way child processes are spawned - it can only pass options to the main process when starting it.
See also http://pavelpolyakov.com/2016/05/01/webstorm-npm-tasks-debug/ - you may find this article helpful
answered Nov 19 at 16:26
lena
49.4k37077
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
No; adding $NODE_DEBUG_OPTION to package.json manually is the only way to debug the application started via npm script, because you have to make sure that Node.js process you'd like to debug is started with appropriate debug options (--debug-brk, --inspect-brk, etc), and the IDE can't control the way child processes are spawned - it can only pass options to the main process when starting it.
See also http://pavelpolyakov.com/2016/05/01/webstorm-npm-tasks-debug/ - you may find this article helpful
answered Nov 19 at 16:26
lena
49.4k37077
add a comment |
up vote
1
down vote
No; adding $NODE_DEBUG_OPTION to package.json manually is the only way to debug the application started via npm script, because you have to make sure that Node.js process you'd like to debug is started with appropriate debug options (--debug-brk, --inspect-brk, etc), and the IDE can't control the way child processes are spawned - it can only pass options to the main process when starting it.
See also http://pavelpolyakov.com/2016/05/01/webstorm-npm-tasks-debug/ - you may find this article helpful
answered Nov 19 at 16:26
lena
49.4k37077
add a comment |
up vote
1
down vote
up vote
1
down vote
No; adding $NODE_DEBUG_OPTION to package.json manually is the only way to debug the application started via npm script, because you have to make sure that Node.js process you'd like to debug is started with appropriate debug options (--debug-brk, --inspect-brk, etc), and the IDE can't control the way child processes are spawned - it can only pass options to the main process when starting it.
See also http://pavelpolyakov.com/2016/05/01/webstorm-npm-tasks-debug/ - you may find this article helpful
answered Nov 19 at 16:26
lena
49.4k37077
No; adding $NODE_DEBUG_OPTION to package.json manually is the only way to debug the application started via npm script, because you have to make sure that Node.js process you'd like to debug is started with appropriate debug options (--debug-brk, --inspect-brk, etc), and the IDE can't control the way child processes are spawned - it can only pass options to the main process when starting it.
See also http://pavelpolyakov.com/2016/05/01/webstorm-npm-tasks-debug/ - you may find this article helpful
answered Nov 19 at 16:26
lena
49.4k37077
answered Nov 19 at 16:26
lena
49.4k37077
answered Nov 19 at 16:26
lena
49.4k37077
answered Nov 19 at 16:26
lena
49.4k37077
49.4k37077
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378435%2fdebugging-npm-scripts-without-modifying-package-json%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
