usernamehw/vscode-error-lens

VSCode extension that enhances display of errors and warnings.

View on GitHub ↗Jump to charts ↓Open shareable report →

usernamehw/vscode-error-lens has 800+ stars and 40+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 11, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 8th, 2026
Created on May 15th, 2019
Open Issues & Pull Requests: 16 (+0)
GitHub issues: Enabled
Number of forks: 48
Total Stargazers: 842 (+0)
Total Subscribers: 4 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.8 hours
Mean response time: 30.2 days
90th percentile: 31.0 days
Tracked items: 60

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 0
Closed in 7 days: 2
Avg open age: 628 days
Stale 30+ days: 12
Stale 90+ days: 10

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (9)
  • feature-request (8)
  • upstream (3)
  • oof (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

ErrorLens is a Visual Studio Code extension that enhances the display of errors and warnings by making diagnostics more visually prominent throughout the editor.

The extension solves the problem of diagnostics being easy to miss or hard to locate by applying multiple visual treatments to lines containing errors or warnings. It highlights entire lines where diagnostics occur, appends diagnostic messages as inline text at the end of those lines, displays icons in the gutter, and shows messages in the status bar. This multi-layered approach ensures that problems are immediately visible without requiring the developer to hover over or navigate to specific locations.

The tool suits developers who want faster error detection and reduced context-switching during coding. It works well in projects using any language supported by VSCode's language servers and linters. The extension provides granular control through commands to toggle different diagnostic levels independently—errors, warnings, info messages, and hints can each be enabled or disabled. Additional commands allow searching for problems in a browser, selecting problem ranges, copying problem messages or codes, excluding specific problems, disabling lines for linter rules, and finding rule definitions in local linter configuration files. The extension supports workspace-level exclusions and offers customization through settings that control comment formats, linter file paths, and search query behavior.

Development activity shows consistent engagement with the codebase through regular updates to both features and settings. The project maintains a substantial command set with fifteen distinct operations, indicating active refinement of user workflows. The settings configuration is extensive with seventy-six configurable options, suggesting the maintainer prioritizes user customization and adaptation to different development environments. Bug fixes and feature additions appear to be addressed as they arise, reflecting ongoing maintenance of the extension's core functionality.