vscode-js-debug/.vscode/launch.json

190 строки
4.9 KiB
JSON
Исходник Обычный вид История

2019-07-26 00:14:00 +03:00
{
2019-06-21 23:51:30 +03:00
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Generate CDP API",
"program": "${workspaceFolder}/dist/src/build/generateCdp.js"
},
2019-06-26 21:13:46 +03:00
{
"type": "node",
"request": "launch",
"name": "Generate DAP API",
"program": "${workspaceFolder}/dist/src/build/generateDap.js"
2019-06-26 21:13:46 +03:00
},
{
"type": "node",
"request": "launch",
"name": "Debug Server",
"program": "${workspaceFolder}/dist/src/debugServerMain.js",
"args": [
"4711"
]
// "preLaunchTask": "npm: watch"
},
{
"type": "node",
"request": "launch",
"name": "Debug Server (Flat Session)",
"trace": true,
"program": "${workspaceFolder}/dist/src/flatSessionLauncher.js",
"args": [
"4712"
],
"skipFiles": [
"<node_internals>/**/*.js"
]
// "preLaunchTask": "npm: watch"
},
{
"type": "node",
"request": "launch",
"name": "Debug Server (VS Server)",
"trace": true,
"program": "${workspaceFolder}/dist/src/vsDebugServer.js",
"args": [
"4712"
],
"skipFiles": [
"<node_internals>/**/*.js"
]
// "preLaunchTask": "npm: watch"
},
{
"type": "node",
"request": "launch",
"name": "Debug Server (DAP)",
"trace": true,
"program": "${workspaceFolder}/dist/src/dapDebugServer.js",
"skipFiles": [
"<node_internals>/**/*.js"
]
// "preLaunchTask": "npm: watch"
},
2019-06-21 23:51:30 +03:00
{
"name": "Extension",
"type": "extensionHost",
2019-06-21 23:51:30 +03:00
"request": "launch",
"skipFiles": [
"<node_internals>/**"
],
2019-06-21 23:51:30 +03:00
"args": [
2019-11-08 21:20:48 +03:00
"--enable-proposed-api=ms-vscode.js-debug",
"--extensionDevelopmentPath=${workspaceFolder}/dist"
],
2019-06-21 23:51:30 +03:00
"outFiles": [
"${workspaceFolder}/dist/**/*.js"
]
// "preLaunchTask": "npm: watch"
},
fix: get the package build target working (#73) * fix: get the package build target working These changes get both the parcel bundling and vsix build targets working together. A few changes to note: - Separated the packaging phase to use the dist folder instead of out. This helps keep packaging completely separate from the normal debug/dev builds - As a result of the above change, the vsce package command now runs inside of the dist folder, so we need to copy any other needed files there as well (atm that's package.json, package.nls.json, and LICENSE) - Changed the gulpfile to use the command-line version of vsce instead of the js lib. I found the js version very hard to debug because gulp tends to swallow console.log statements, so the build would fail with zero diagnostic output. Using the command line api solves that problem and makes builds easier to debug. - Moved the tsconfig out of the src dir and into the root. I did this mainly because we are referencing the package.json in some parts of the code now, and if we use require(''), parcel can't resolve it, because we've gone one level deeper (from src to out/src). The solution to this is to use typescript import to import package.json. On compile, ts knows to change the relative path based on the output dir. But in order to let ts actually do this, we have to change the root of the ts project so that package.json is inside of it. * chore: switch from parcel to webpack Parcel seems to have issues with the vscode dependency on Mac/Linux? * fix: always use forward slashes in gulp src/dest gulp seems to be able to handle backslashes on windows, but is not always consistent in behavior (e.g. in this case, on windows gulp would copy the resources directory fully recursively, whereas on mac/linux it would only copy the files, not preserving the directory structure) * fix: don't stub __dirname, copy shell scripts
2019-11-08 20:12:02 +03:00
{
"name": "Extension With Local DAP",
fix: get the package build target working (#73) * fix: get the package build target working These changes get both the parcel bundling and vsix build targets working together. A few changes to note: - Separated the packaging phase to use the dist folder instead of out. This helps keep packaging completely separate from the normal debug/dev builds - As a result of the above change, the vsce package command now runs inside of the dist folder, so we need to copy any other needed files there as well (atm that's package.json, package.nls.json, and LICENSE) - Changed the gulpfile to use the command-line version of vsce instead of the js lib. I found the js version very hard to debug because gulp tends to swallow console.log statements, so the build would fail with zero diagnostic output. Using the command line api solves that problem and makes builds easier to debug. - Moved the tsconfig out of the src dir and into the root. I did this mainly because we are referencing the package.json in some parts of the code now, and if we use require(''), parcel can't resolve it, because we've gone one level deeper (from src to out/src). The solution to this is to use typescript import to import package.json. On compile, ts knows to change the relative path based on the output dir. But in order to let ts actually do this, we have to change the root of the ts project so that package.json is inside of it. * chore: switch from parcel to webpack Parcel seems to have issues with the vscode dependency on Mac/Linux? * fix: always use forward slashes in gulp src/dest gulp seems to be able to handle backslashes on windows, but is not always consistent in behavior (e.g. in this case, on windows gulp would copy the resources directory fully recursively, whereas on mac/linux it would only copy the files, not preserving the directory structure) * fix: don't stub __dirname, copy shell scripts
2019-11-08 20:12:02 +03:00
"type": "extensionHost",
"request": "launch",
"skipFiles": [
"<node_internals>/**"
],
fix: get the package build target working (#73) * fix: get the package build target working These changes get both the parcel bundling and vsix build targets working together. A few changes to note: - Separated the packaging phase to use the dist folder instead of out. This helps keep packaging completely separate from the normal debug/dev builds - As a result of the above change, the vsce package command now runs inside of the dist folder, so we need to copy any other needed files there as well (atm that's package.json, package.nls.json, and LICENSE) - Changed the gulpfile to use the command-line version of vsce instead of the js lib. I found the js version very hard to debug because gulp tends to swallow console.log statements, so the build would fail with zero diagnostic output. Using the command line api solves that problem and makes builds easier to debug. - Moved the tsconfig out of the src dir and into the root. I did this mainly because we are referencing the package.json in some parts of the code now, and if we use require(''), parcel can't resolve it, because we've gone one level deeper (from src to out/src). The solution to this is to use typescript import to import package.json. On compile, ts knows to change the relative path based on the output dir. But in order to let ts actually do this, we have to change the root of the ts project so that package.json is inside of it. * chore: switch from parcel to webpack Parcel seems to have issues with the vscode dependency on Mac/Linux? * fix: always use forward slashes in gulp src/dest gulp seems to be able to handle backslashes on windows, but is not always consistent in behavior (e.g. in this case, on windows gulp would copy the resources directory fully recursively, whereas on mac/linux it would only copy the files, not preserving the directory structure) * fix: don't stub __dirname, copy shell scripts
2019-11-08 20:12:02 +03:00
"args": [
2019-11-08 21:20:48 +03:00
"--enable-proposed-api=ms-vscode.js-debug",
"--extensionDevelopmentPath=${workspaceFolder}/dist"
fix: get the package build target working (#73) * fix: get the package build target working These changes get both the parcel bundling and vsix build targets working together. A few changes to note: - Separated the packaging phase to use the dist folder instead of out. This helps keep packaging completely separate from the normal debug/dev builds - As a result of the above change, the vsce package command now runs inside of the dist folder, so we need to copy any other needed files there as well (atm that's package.json, package.nls.json, and LICENSE) - Changed the gulpfile to use the command-line version of vsce instead of the js lib. I found the js version very hard to debug because gulp tends to swallow console.log statements, so the build would fail with zero diagnostic output. Using the command line api solves that problem and makes builds easier to debug. - Moved the tsconfig out of the src dir and into the root. I did this mainly because we are referencing the package.json in some parts of the code now, and if we use require(''), parcel can't resolve it, because we've gone one level deeper (from src to out/src). The solution to this is to use typescript import to import package.json. On compile, ts knows to change the relative path based on the output dir. But in order to let ts actually do this, we have to change the root of the ts project so that package.json is inside of it. * chore: switch from parcel to webpack Parcel seems to have issues with the vscode dependency on Mac/Linux? * fix: always use forward slashes in gulp src/dest gulp seems to be able to handle backslashes on windows, but is not always consistent in behavior (e.g. in this case, on windows gulp would copy the resources directory fully recursively, whereas on mac/linux it would only copy the files, not preserving the directory structure) * fix: don't stub __dirname, copy shell scripts
2019-11-08 20:12:02 +03:00
],
"env": {
"JS_DEBUG_USE_LOCAL_DAP_PORT": "8123"
},
"outFiles": [
"${workspaceFolder}/dist/**/*.js"
]
fix: get the package build target working (#73) * fix: get the package build target working These changes get both the parcel bundling and vsix build targets working together. A few changes to note: - Separated the packaging phase to use the dist folder instead of out. This helps keep packaging completely separate from the normal debug/dev builds - As a result of the above change, the vsce package command now runs inside of the dist folder, so we need to copy any other needed files there as well (atm that's package.json, package.nls.json, and LICENSE) - Changed the gulpfile to use the command-line version of vsce instead of the js lib. I found the js version very hard to debug because gulp tends to swallow console.log statements, so the build would fail with zero diagnostic output. Using the command line api solves that problem and makes builds easier to debug. - Moved the tsconfig out of the src dir and into the root. I did this mainly because we are referencing the package.json in some parts of the code now, and if we use require(''), parcel can't resolve it, because we've gone one level deeper (from src to out/src). The solution to this is to use typescript import to import package.json. On compile, ts knows to change the relative path based on the output dir. But in order to let ts actually do this, we have to change the root of the ts project so that package.json is inside of it. * chore: switch from parcel to webpack Parcel seems to have issues with the vscode dependency on Mac/Linux? * fix: always use forward slashes in gulp src/dest gulp seems to be able to handle backslashes on windows, but is not always consistent in behavior (e.g. in this case, on windows gulp would copy the resources directory fully recursively, whereas on mac/linux it would only copy the files, not preserving the directory structure) * fix: don't stub __dirname, copy shell scripts
2019-11-08 20:12:02 +03:00
// "preLaunchTask": "npm: watch"
},
{
"name": "Extension and Auto Launch",
"type": "pwa-extensionHost",
"request": "launch",
"skipFiles": [
"<node_internals>/**"
],
"args": [
"--enable-proposed-api=ms-vscode.js-debug",
"--extensionDevelopmentPath=${workspaceFolder}/../vscode/extensions/debug-auto-launch",
"--extensionDevelopmentPath=${workspaceFolder}/dist"
],
"resolveSourceMapLocations": [
"${workspaceFolder}/**",
"${workspaceFolder}/../vscode/extensions/debug-auto-launch/out/**",
"!**/node_modules/**"
],
"outFiles": [
"${workspaceFolder}/dist/**/*.js",
"${workspaceFolder}/../vscode-js-debug-companion/out/**/*.js"
]
},
{
"name": "Extension and Companion",
"type": "extensionHost",
"request": "launch",
"skipFiles": [
"<node_internals>/**"
],
"args": [
"--enable-proposed-api=ms-vscode.js-debug",
"--extensionDevelopmentPath=${workspaceFolder}/../vscode-js-debug-companion",
"--extensionDevelopmentPath=${workspaceFolder}/dist"
],
"env": {
"JS_DEBUG_USE_COMPANION": "1"
},
"trace": true,
"resolveSourceMapLocations": [
"${workspaceFolder}/**",
"${workspaceFolder}/../vscode-js-debug-companion/**",
"!**/node_modules/**"
],
"outFiles": [
"${workspaceFolder}/dist/**/*.js",
"${workspaceFolder}/../vscode-js-debug-companion/out/**/*.js"
]
2019-06-21 23:51:30 +03:00
},
{
"name": "Run Golden Tests",
"type": "pwa-extensionHost",
"request": "launch",
"skipFiles": [
"<node_internals>/**"
],
"args": [
"--extensionDevelopmentPath=${workspaceFolder}/dist",
"--extensionTestsPath=${workspaceFolder}/dist/src/testRunner"
2019-06-21 23:51:30 +03:00
],
"outFiles": [
"${workspaceFolder}/dist/**/*.js"
]
},
{
"name": "Run Unit Tests",
"type": "pwa-node",
"request": "launch",
"skipFiles": [
"<node_internals>/**"
],
"runtimeExecutable": "${workspaceFolder}/node_modules/.bin/mocha",
"runtimeArgs": [
"--config",
".mocharc.unit.js"
],
"outFiles": [
"${workspaceFolder}/dist/**/*.js"
]
fix: get the package build target working (#73) * fix: get the package build target working These changes get both the parcel bundling and vsix build targets working together. A few changes to note: - Separated the packaging phase to use the dist folder instead of out. This helps keep packaging completely separate from the normal debug/dev builds - As a result of the above change, the vsce package command now runs inside of the dist folder, so we need to copy any other needed files there as well (atm that's package.json, package.nls.json, and LICENSE) - Changed the gulpfile to use the command-line version of vsce instead of the js lib. I found the js version very hard to debug because gulp tends to swallow console.log statements, so the build would fail with zero diagnostic output. Using the command line api solves that problem and makes builds easier to debug. - Moved the tsconfig out of the src dir and into the root. I did this mainly because we are referencing the package.json in some parts of the code now, and if we use require(''), parcel can't resolve it, because we've gone one level deeper (from src to out/src). The solution to this is to use typescript import to import package.json. On compile, ts knows to change the relative path based on the output dir. But in order to let ts actually do this, we have to change the root of the ts project so that package.json is inside of it. * chore: switch from parcel to webpack Parcel seems to have issues with the vscode dependency on Mac/Linux? * fix: always use forward slashes in gulp src/dest gulp seems to be able to handle backslashes on windows, but is not always consistent in behavior (e.g. in this case, on windows gulp would copy the resources directory fully recursively, whereas on mac/linux it would only copy the files, not preserving the directory structure) * fix: don't stub __dirname, copy shell scripts
2019-11-08 20:12:02 +03:00
},
{
"name": "Debug Gulp",
"type": "node",
"request": "launch",
"program": "${workspaceFolder}/node_modules/gulp/bin/gulp.js",
"args": [
"move-bundle-files"
]
2019-06-21 23:51:30 +03:00
}
]
}