npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

lazybuilder-cli

v0.2.0

Published

TUI + CLI for diagnosing .NET / MSBuild / C++ / CMake build environments and executing builds. Designed as a tool for AI dev loops (Claude Code, Cursor, …) and as a human-friendly TUI.

Readme

LazyBuilder - .NET / MSBuild / C++ Build TUI

Terminal UI for diagnosing build environments and executing builds without Visual Studio IDE.

Features

  • Environment Detection: .NET SDK, MSBuild, Visual Studio, C++ Toolchain, Windows SDK (7/8.1/10/11), CMake, Ninja, Git
  • Project Scanning: .sln, .csproj, .vcxproj, CMakeLists.txt auto-discovery with type classification
  • Configuration Manager: Parses solution/project Configuration|Platform pairs for build target selection
  • Build Execution: dotnet build, msbuild, cmake --build with real-time streaming output
  • Diagnostics: Pre-build environment validation with actionable fix suggestions
  • Log Viewer: Filtered log output with error/warning parsing and summary
  • Auto Update: Checks npm registry (or git origin if cloned) on startup
  • Cross-platform: Windows primary, Linux/macOS partial support
  • AI-Tool Ready: Headless flags + JSON envelope contract — see agent.md and docs/agents/ on GitHub

Requirements

  • Node.js >= 20.0.0
  • Git (for auto-update feature)
  • Terminal with Unicode support (Windows Terminal recommended)

Installation

Recommended (npm — global)

npm install -g lazybuilder-cli
lazybuilder           # launch the TUI

Update

lazybuilder --check-update   # JSON: { updateAvailable, currentVersion, latestVersion, mode }
lazybuilder --update         # auto-update (npm or git, depending on install mode)

# manual fallback:
npm install -g lazybuilder-cli@latest

From source (Windows)

git clone https://github.com/rhkdguskim/lazybuilder.git
cd lazybuilder
install.bat

From source (Linux / macOS)

git clone https://github.com/rhkdguskim/lazybuilder.git
cd lazybuilder
./install.sh

Manual from source

git clone https://github.com/rhkdguskim/lazybuilder.git
cd lazybuilder
npm install
npm run build
npm link

Development (no install)

git clone https://github.com/rhkdguskim/lazybuilder.git
cd lazybuilder
npm install
npm run dev

Usage

Launch the TUI:

lazybuilder

On startup, the tool will:

  1. Check for updates from GitHub (prompts to update if available)
  2. Scan your build environment (.NET, MSBuild, C++, CMake, etc.)
  3. Scan the current directory for projects and solutions
  4. Run diagnostics to detect missing tools or configuration issues

Keyboard Shortcuts

| Key | Action | |-----|--------| | Ctrl+1~8 | Switch to tab directly | | Ctrl+←→ | Previous/Next tab | | ↑↓ | Navigate lists | | ←→ | Change selection (Build tab) | | Enter | Confirm / Execute build | | Esc | Cancel build | | Tab | Switch filter | | f | Toggle log follow mode | | q | Quit |

Tabs

| # | Tab | Description | |---|-----|-------------| | 1 | Overview | Build environment status at a glance | | 2 | Environment | Detailed tool/SDK info by category (.NET, MSBuild, VS, C++, Windows SDK, CMake, Packages) | | 3 | Projects | Scanned solutions and projects with metadata, TFM, recommended build command | | 4 | Build | Configuration manager with Configuration/Platform selection, command preview, execute | | 5 | Diagnostics | Environment issues with severity filtering and fix suggestions | | 6 | Logs | Real-time build log with error/warning filtering | | 7 | History | Past build results | | 8 | Settings | Application configuration |

Uninstall

npm unlink -g lazybuilder

Tech Stack

Project Structure

src/
├── domain/          # Types, enums, diagnostic rules
├── infrastructure/  # Process runner, detectors, parsers, adapters
├── application/     # Service orchestration
└── ui/              # React/Ink components, hooks, store

Documentation

Agent integration guides and architecture docs live in the GitHub repo, not the npm tarball:

License

MIT