Closed
Description
This is an issue in the task configuration of vscode-java-debug
itself (not a problem using the extension). The "Launch Extension" configuration runs a preLaunchTask "npm: watch". That task is configured to run in the background, but the beginsPattern
and endsPatterns
are incorrect. They don't match any of webpack's output and so the launch config hangs and never launches the extension host.
For the current webpack, I recommend adding this to webpack.config.js
:
infrastructureLogging: {
level: 'log'
}
And then setting the problemMatcher
:
"beginsPattern": "Compiler '[^']+' starting",
"endsPattern": "Compiler '[^']+' finished"
I'll submit a PR with these changes.
Environment
- Operating System: Windows 10
- JDK version: 17.0.2
- Visual Studio Code version: 1.65.1
- Java extension version: 1.4.0
- Java Debugger extension version: 0.38.0
Steps To Reproduce
Following steps in CONTRIBUTING.md
:
git checkout https://github.com/Microsoft/vscode-java-debug.git
cd vscode-java-debug
npm install
code .
- In vscode, press F5 to run the 'Launch Extension' launch configuration.
Current Result
A new "watch" task terminal appears. Wait for it, but the extension host does not appear.
Expected Result
After the webpack build finishes, the extension host should launch.