You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- run node process `node --inspect-brk --nolazy <path to script>`
- run vscode debugger, restart mode is on which will make vscode attach automatically when the tool watching files restarts the process.
While the option Auto Attach in VSCode settings.json doesn't support processes in the vscode integrated console.
e.g. node --inspect-brk --nolazy ./node_modules/@deployment/scriptManager/source/entrypoint/cli test "({ testPath: './distribution/test/script.test.js' })"
e.g. yarn run scriptManager test "({ testPath: ['./distribution/test'], shouldDebugger: true, shouldCompileTest: false })"
"restart": true, // restart debug session when terminated e.g. on failure.
// "useWSL": false, //! Do not use this flag as it will mess the breakpoints locations and cause them to `jump` to different locations.
"stopOnEntry": true, // break immediately.
"autoAttachChildProcesses": true, // track all subprocesses of debuggee and automatically attach to those that are launched in debug mode
"trace": false/* true || "verbose" */ , // enable diagnostic output - outputs protocol communication to txt file (path is printed in debug console).
"internalConsoleOptions": "neverOpen",
"sourceMaps": true, // will read source maps even Babel runtime transformed.
"localRoot": "${workspaceFolder}", // on Windows system
"remoteRoot": "${command:extension.vscode-wsl-workspaceFolder}", // path in WSL
/**
fix mappings between Windows (location on disk) and WSL (source map paths). This will find the source file in disk location instead of transferring it through the debugger socker.
