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

open-ready

v0.1.9

Published

Smart dev server launcher: error→AI search, success→auto-open browser. Any CLI tool.

Downloads

636

Readme

open-ready

Smart dev server launcher that watches your server's output and automatically opens the browser when ready — or opens an AI assistant with the error context when something goes wrong.

Works with Next.js, Vite, and any CLI-based dev server.

Install

npm install -g open-ready
# or use without installing:
npx open-ready <your-dev-command>

Usage

open-ready <command> [options]

Examples

open-ready npm run dev
open-ready bun run dev
open-ready vite
open-ready next dev

Options

| Flag | Default | Description | |------|---------|-------------| | --ai-base <url> | https://perplexity.ai?q= | AI assistant base URL to open on error | | --noAi | false | Disable opening AI on error | | --noOpen | false | Disable opening browser when ready | | --pollDelay <ms> | 1200 | How often to poll the log for ready/error signals |

Disable AI on error

open-ready npm run dev --noAi

Use a different AI assistant

open-ready npm run dev --ai-base "https://chatgpt.com/?q="

How it works

  1. Spawns your dev command and pipes its stdout/stderr to a log file
  2. Polls the log every pollDelay ms looking for:
    • Error signal — lines matching error, failed, exception, SyntaxError, or
    • Ready signal — lines matching ready - started server or Ready in Xms
  3. On error: extracts up to ~1000 chars of surrounding context and opens your AI assistant with a pre-filled prompt explaining the error and asking for a fix
  4. On ready: waits for the port to be reachable, then opens the local URL in your default browser

For Next.js projects, the log is written to .next/port.log; otherwise open-when-ready.log in the current directory.

License

MIT