Neovim LSP & in-editor resource management

• 

  Checking stats of Baseline

• 

  Baseline API Call in editor

• 

  Command line checking

• 

  LSP in action

Inspiration

As a developer passionate about code quality and consistency, I noticed that keeping projects in sync with evolving best practices, especially those recommended by Google Baseline; was a constant struggle. Manual checks were tedious, and existing tools didn’t offer enough automation or transparency for fast-moving teams.

The Challenge

When I set out to build baseline-checker, my main challenge was integrating Google Baseline standards into everyday development workflows. Parsing Baseline rules and keeping them updated in real-time proved tricky, especially as Google regularly introduced new features and guidelines. I also wanted the tool to be lightweight, language-agnostic, and easy for developers to use right inside their editors.

Another hurdle was providing seamless access to both local and remote Baseline data via an API, ensuring that teams could see up-to-date recommendations and compliance reports without jumping between tools. Making the tool work reliably with Neovim’s LSP and in-editor resource management pushed me to learn more about plugin development and cross-platform compatibility.

The Solution

I created baseline-checker to automate the detection and enforcement of Baseline rules in projects, directly from the editor. The tool fetches real-time updates, calls APIs for local and remote data, and surfaces actionable insights to developers as they code. This empowers teams to stay compliant, move faster, and maintain high standards without extra overhead.

Why It Matters

With baseline-checker, developers can focus on building features, not chasing ever-changing standards. The project represents my commitment to better workflows, smarter automation, and continuous improvement in software quality.

Built With

• baseline
• lsp
• lua
• neovim
• nvim