How to debug 2 script together?
I'm using VSCode and have a js project. I'm managing the build/bundle/test process via npm.
This is the package.json file:
{
/* ... */
"scripts": {
"bundle": "webpack",
"minify": "node bin/minify",
"build": "npm run bundle && npm run minify",
"bundle-debug": "node --inspect-brk ./node_modules/webpack/bin/webpack.js",
"minify-debug": "node --inspect-brk bin/minify",
"build-debug": "npm run bundle-debug && npm run minify-debug"
}
}
This is the launch.json file that I use for debugging:
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Debug The Build Task",
"runtimeExecutable": "npm",
"runtimeArgs": ["run-script", "build-debug"]
}
]
}
So, my question is: When I hit F5 to debug the application with the configuration above, I can only hit the breakpoint on the file webpack.config.js and can never hit the breakpoint on the file bin/minify. So, after some test I realized that the joining the scripts with && sign causes it not to debug the second script. So that means if I change the order of the "build-debug" script as below, then, breakpoint hits on bin/minify file but not on webpack.config.js: just the opposite....
"build-debug": "npm run minify-debug && npm run bundle-debug"
As a solution VSCode offers compounds. But, I want these 2 scripts that is forming "build-debug" task in the order it's given. And making a compound in the launch.json means splitting 1 debug config into 2 + the compund of the 2 configs. And the order of the execution that is defined on the package.json is not sync with the order defined in compound config. That means if I change "build-debug" script then I have to change compound config also.
1) Are there any way to solve this problem?
2) Are there any way of debugging the "build" script directly without defining it's copies named "build-debug"?
node.js npm visual-studio-code vscode-debugger vscode-tasks
asked Nov 21 '18 at 11:55
rebulanyumrebulanyum
127217
add a comment |
I'm using VSCode and have a js project. I'm managing the build/bundle/test process via npm.
This is the package.json file:
{
/* ... */
"scripts": {
"bundle": "webpack",
"minify": "node bin/minify",
"build": "npm run bundle && npm run minify",
"bundle-debug": "node --inspect-brk ./node_modules/webpack/bin/webpack.js",
"minify-debug": "node --inspect-brk bin/minify",
"build-debug": "npm run bundle-debug && npm run minify-debug"
}
}
This is the launch.json file that I use for debugging:
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Debug The Build Task",
"runtimeExecutable": "npm",
"runtimeArgs": ["run-script", "build-debug"]
}
]
}
So, my question is: When I hit F5 to debug the application with the configuration above, I can only hit the breakpoint on the file webpack.config.js and can never hit the breakpoint on the file bin/minify. So, after some test I realized that the joining the scripts with && sign causes it not to debug the second script. So that means if I change the order of the "build-debug" script as below, then, breakpoint hits on bin/minify file but not on webpack.config.js: just the opposite....
"build-debug": "npm run minify-debug && npm run bundle-debug"
As a solution VSCode offers compounds. But, I want these 2 scripts that is forming "build-debug" task in the order it's given. And making a compound in the launch.json means splitting 1 debug config into 2 + the compund of the 2 configs. And the order of the execution that is defined on the package.json is not sync with the order defined in compound config. That means if I change "build-debug" script then I have to change compound config also.
1) Are there any way to solve this problem?
2) Are there any way of debugging the "build" script directly without defining it's copies named "build-debug"?
node.js npm visual-studio-code vscode-debugger vscode-tasks
asked Nov 21 '18 at 11:55
rebulanyumrebulanyum
127217
add a comment |
I'm using VSCode and have a js project. I'm managing the build/bundle/test process via npm.
This is the package.json file:
{
/* ... */
"scripts": {
"bundle": "webpack",
"minify": "node bin/minify",
"build": "npm run bundle && npm run minify",
"bundle-debug": "node --inspect-brk ./node_modules/webpack/bin/webpack.js",
"minify-debug": "node --inspect-brk bin/minify",
"build-debug": "npm run bundle-debug && npm run minify-debug"
}
}
This is the launch.json file that I use for debugging:
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Debug The Build Task",
"runtimeExecutable": "npm",
"runtimeArgs": ["run-script", "build-debug"]
}
]
}
So, my question is: When I hit F5 to debug the application with the configuration above, I can only hit the breakpoint on the file webpack.config.js and can never hit the breakpoint on the file bin/minify. So, after some test I realized that the joining the scripts with && sign causes it not to debug the second script. So that means if I change the order of the "build-debug" script as below, then, breakpoint hits on bin/minify file but not on webpack.config.js: just the opposite....
"build-debug": "npm run minify-debug && npm run bundle-debug"
As a solution VSCode offers compounds. But, I want these 2 scripts that is forming "build-debug" task in the order it's given. And making a compound in the launch.json means splitting 1 debug config into 2 + the compund of the 2 configs. And the order of the execution that is defined on the package.json is not sync with the order defined in compound config. That means if I change "build-debug" script then I have to change compound config also.
1) Are there any way to solve this problem?
2) Are there any way of debugging the "build" script directly without defining it's copies named "build-debug"?
node.js npm visual-studio-code vscode-debugger vscode-tasks
asked Nov 21 '18 at 11:55
rebulanyumrebulanyum
127217
I'm using VSCode and have a js project. I'm managing the build/bundle/test process via npm.
This is the package.json file:
{
/* ... */
"scripts": {
"bundle": "webpack",
"minify": "node bin/minify",
"build": "npm run bundle && npm run minify",
"bundle-debug": "node --inspect-brk ./node_modules/webpack/bin/webpack.js",
"minify-debug": "node --inspect-brk bin/minify",
"build-debug": "npm run bundle-debug && npm run minify-debug"
}
}
This is the launch.json file that I use for debugging:
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Debug The Build Task",
"runtimeExecutable": "npm",
"runtimeArgs": ["run-script", "build-debug"]
}
]
}
So, my question is: When I hit F5 to debug the application with the configuration above, I can only hit the breakpoint on the file webpack.config.js and can never hit the breakpoint on the file bin/minify. So, after some test I realized that the joining the scripts with && sign causes it not to debug the second script. So that means if I change the order of the "build-debug" script as below, then, breakpoint hits on bin/minify file but not on webpack.config.js: just the opposite....
"build-debug": "npm run minify-debug && npm run bundle-debug"
As a solution VSCode offers compounds. But, I want these 2 scripts that is forming "build-debug" task in the order it's given. And making a compound in the launch.json means splitting 1 debug config into 2 + the compund of the 2 configs. And the order of the execution that is defined on the package.json is not sync with the order defined in compound config. That means if I change "build-debug" script then I have to change compound config also.
1) Are there any way to solve this problem?
2) Are there any way of debugging the "build" script directly without defining it's copies named "build-debug"?
node.js npm visual-studio-code vscode-debugger vscode-tasks
node.js npm visual-studio-code vscode-debugger vscode-tasks
asked Nov 21 '18 at 11:55
rebulanyumrebulanyum
127217
asked Nov 21 '18 at 11:55
rebulanyumrebulanyum
127217
asked Nov 21 '18 at 11:55
rebulanyumrebulanyum
127217
asked Nov 21 '18 at 11:55
rebulanyumrebulanyum
127217
asked Nov 21 '18 at 11:55
rebulanyumrebulanyum
127217
127217
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53411512%2fhow-to-debug-2-script-together%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2f53411512%2fhow-to-debug-2-script-together%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
