Baseline Lens CLI
Baseline compatibility checking for your pipeline, not just your editor.
The Problem
Editor-level compatibility checks are only as good as the discipline of every individual developer remembering to look at them before committing.
Baseline Lens CLI extends the same compatibility checking into the places an editor extension can't reach: pre-commit hooks and CI/CD pipelines. It auto-detects React, Vue, or Angular projects and generates optimal settings automatically, so setup is close to zero-config for common stacks.
It can generate ready-to-use configuration for GitHub Actions, GitLab CI, and Azure Pipelines directly, turning 'someone should really check this before we ship' into an automatic step that runs on every commit or pull request, whether or not the person pushing the code remembered to look at their editor's inline warnings.
When both tools are installed, the VS Code extension automatically detects the CLI in a project and unlocks enhanced features — the two are designed to work as one system, not two overlapping tools.
Who It's For
Teams who want compatibility checks enforced automatically in CI/CD, not just visible to whoever happens to be looking at their editor.
"Baseline Lens in the editor is only as reliable as the person looking at it. The CLI exists so compatibility gets checked even when nobody's watching — on commit, in CI, every time."
— Founder, Naviware
Features
- •Automatic compatibility checking on commit via git hooks
- •Generates ready-to-use CI/CD configuration for GitHub Actions, GitLab CI, and Azure Pipelines
- •Auto-detects React, Vue, or Angular projects and generates optimal settings
- •Project-wide compatibility analysis and reporting from the command line
- •Automatically detected by the Baseline Lens VS Code extension to unlock enhanced features
Built With
Ready to try Baseline Lens CLI?
View on npm