A Visual Studio Code extension that monitors build log files for errors and displays them in VS Code's Problems panel.
Auto monitoring: Watches build log files for changes and automatically parses new content
Custom wildcard log paths: Configurable paths to log files including wildcard patterns.
Custom problem patterns: Configurable problem matcher patterns to identify different types of build errors with file locations, line numbers, and severity
VS Code integration: Displays errors in the Problems panel with clickable links to source files. Also supports related information for errors.
Commands
The extension provides the following commands accessible via the Command Palette (Ctrl+Shift+P):
WatchBuildLog: Start Watching Build Log - Begin monitoring the configured log file
Description: Glob-style wildcard patterns for build log files. Patterns can be absolute paths or relative to the project root. Use '*' to match any text in a folder segment.
Scope: Resource (can be set per workspace)
Examples:
"out/*_x64/siso.log" - Matches siso.log in any subfolder of out/ that ends with _x64
"build/*/errors.log" - Matches errors.log in any direct subfolder of build/
"C:/logs/*.log" - Absolute path matching any .log file in C:/logs/
watchbuildlog.autoStart
Type: boolean
Default: true
Description: Automatically start watching when VS Code opens
watchbuildlog.problemMatcherPatterns
Type: array
Description: Problem matcher patterns similar to VS Code's task system. Each pattern defines a regex and capture group indices for extracting error information from build logs.
Usage
Configure log file patterns:
Open VS Code Settings (Ctrl+,)
Search for "watchbuildlog"
Add wildcard patterns to "Log File Path Wildcards" (default includes "out/*/siso_output")
Or add to your settings.json: "watchbuildlog.logFilePathWildcards": ["out/*_x64/siso.log", "build/*/errors.log"]
Start watching: The extension auto-starts by default, or run "Start Watching Build Log" command manually
View errors: Build errors will appear in the Problems panel (Ctrl+Shift+M)
Navigate to errors: Click on errors in the Problems panel to jump to the source location