A developer frustrated by outdated and missing tooling in Visual Studio Code has independently built two extensions aimed at improving the daily workflows of infrastructure engineers: one adding full Language Server Protocol support for HAProxy configuration files, and another enabling inline inspection of SSL/TLS certificates without leaving the editor.
Juan Torchia, a software developer who describes himself as a daily HAProxy user, published two VS Code extensions in April 2026 after reaching what he called a breaking point with the state of available tooling — a feeling familiar to many developers who work at the intersection of networking, security, and modern development environments.
The first extension addresses HAProxy, the widely-used open-source load balancer and proxy server. The only existing VS Code extension for HAProxy syntax highlighting had not received a commit since 2019, despite HAProxy releasing multiple major versions in the intervening years. Torchia notes that significant changes — including new directives, deprecated options, and revised behaviours — had accumulated in that time, leaving the extension effectively obsolete.
"Five years without a single change. HAProxy went from version 2.0 to 3.1 in that time," Torchia wrote in a post describing the project. "And the extension just sat there, frozen in time like a digital mummy."
Rather than simply refreshing keyword lists, Torchia built a full Language Server Protocol (LSP) implementation that understands HAProxy's section-based configuration model. The extension distinguishes between directives that are valid in frontend, backend, listen, global, and other sections — context-sensitive knowledge that simple grammar-based syntax highlighters cannot provide. The LSP also surfaces diagnostics for deprecated directives.
The second extension, gmm.certview, targets a different pain point: inspecting SSL/TLS certificate files. Torchia described the common scenario of needing to verify a deployed certificate during a production incident, only to be pulled out of the editor and into a terminal to recall and run the correct openssl command. His extension registers as a custom editor for certificate file types — including .pem, .der, .p12, and .pfx — displaying their contents in a structured view directly within VS Code on double-click.
Built on TypeScript and the node-forge cryptographic library, the certificate viewer was deliberately designed to work entirely offline with no external binary dependencies, a consideration Torchia cited as important for developers working in corporate environments with restricted software policies.
Both projects reflect a broader pattern in the developer tooling ecosystem: niche but critical tools often go unmaintained as their original authors move on, leaving users to work around gaps or build alternatives themselves. HAProxy, while perhaps less visible than Nginx or Traefik in developer circles, is widely deployed in financial services, telecommunications, and other high-availability infrastructure contexts.
Torchia's extensions are available on the VS Code Marketplace. Neither project appears to be commercially motivated; both were described as solutions to problems the author encountered directly in his own work.
Analysis
Why This Matters
- Developer tooling gaps in mature but niche infrastructure software are common and often invisible until they cause real operational friction — Torchia's projects highlight how much unmet demand exists just below the surface of popular ecosystems.
- The LSP implementation for HAProxy is particularly significant: context-aware editing assistance can reduce misconfiguration errors in production load balancers, which sit at the critical path of many applications.
- Solo developer extensions filling gaps left by abandoned projects raises questions about long-term maintenance sustainability — who maintains the maintainer?
Background
The Visual Studio Code extension marketplace has grown to host tens of thousands of extensions, but coverage is uneven. Popular languages and frameworks receive robust, frequently updated tooling from both Microsoft and large open-source communities. Infrastructure tools — particularly those associated with older or more specialised ecosystems — often rely on single-author extensions that can fall dormant without notice.
HAProxy has been actively developed since the early 2000s and remains a dominant choice for high-performance load balancing. Its configuration language is expressive and context-sensitive, making it a natural candidate for LSP-based tooling, yet the developer community around it is concentrated in operations and infrastructure roles where editor extension development is not a primary focus.
The SSL certificate landscape has grown considerably more complex since Let's Encrypt democratised HTTPS in 2015. Developers now routinely encounter certificate files in multiple formats across local development, CI/CD pipelines, and Kubernetes secrets — increasing the frequency with which certificate inspection becomes necessary during normal development work.
Key Perspectives
Infrastructure developers: Engineers who work daily with HAProxy or manage certificate-heavy systems stand to benefit directly. Context-aware completion and inline diagnostics reduce the cognitive load of managing complex, hand-edited configuration files.
VS Code ecosystem maintainers: Microsoft and the broader VS Code community benefit when gaps in the marketplace are filled, though the platform has limited mechanisms to ensure long-term maintenance of community extensions — the same abandonment risk applies to Torchia's work as to the projects he replaced.
Critics/Skeptics: Solo-maintained extensions carry inherent sustainability risks. If Torchia moves on or loses interest, these tools could themselves become the abandoned extensions future developers work around. Additionally, parsing cryptographic files within an editor extension — even using a well-regarded library — may give some security-conscious teams pause.
What to Watch
- Adoption and star counts on the VS Code Marketplace and associated GitHub repositories will indicate whether there is sufficient community interest to attract co-maintainers.
- Whether the HAProxy core team or community organisations take an interest in formally endorsing or co-maintaining an LSP-based extension.
- Whether similar LSP efforts emerge for other infrastructure tools — such as Nginx, Envoy, or HAProxy's peers — following the same pattern of community-driven gap-filling.