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

layrr

v2026.5.0

Published

Point, click, and edit any web app with AI

Downloads

220

Readme


The problem

You can see the issue in the browser: the button is too wide, the copy is wrong, the spacing is off, or the component needs a quick behavior change. The slow part is finding the right file, line, and context before your coding agent can make a useful edit.

Layrr sits between your browser and local dev server. It injects a small overlay, maps clicked elements back to source, and gives your coding agent the instruction plus the selected code location.

Install

Install Layrr globally:

npm install -g layrr

Usage

Start your app first:

pnpm dev

Then run Layrr against the dev server port:

layrr --port 3000

Layrr opens a proxied version of your app at http://localhost:4567.

In the browser:

  1. Click one or more elements.
  2. Describe the change you want.
  3. Let the selected coding agent edit the source.
  4. Preview or revert Layrr edits from the overlay history.

For a local checkout:

pnpm install
pnpm build
node dist/cli.js --port 3000

Options

layrr --port <number> [project-root] [options]

| Option | Description | | --- | --- | | -p, --port <number> | Local dev server port. Required. | | --proxy-port <number> | Layrr proxy port. Defaults to 4567. | | --agent <name> | AI agent to use: claude, codex, or gemini. | | --gemini-model <model> | Save and use a Gemini model, for example gemini-2.5-flash. | | --configure-gemini | Reconfigure the Gemini model and API key. | | --no-open | Do not open the browser automatically. | | -h, --help | Show help. |

Agents

Layrr supports:

  • claude - Claude Code
  • codex - Codex CLI
  • gemini - Gemini via Pi coding agent, installed as a Layrr dependency

If no agent is configured, Layrr prompts you to pick one.

To configure Gemini without starting a session:

layrr --configure-gemini

Git History

Layrr uses git as its undo path:

  • initializes a git repo if needed
  • creates an initial snapshot when needed
  • commits successful edits with a [layrr] prefix
  • keeps pre-existing dirty files out of Layrr edit commits
  • lets the overlay preview and revert Layrr edits

License

MIT