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

pi-nvim

v0.1.2

Published

Bridge between pi coding agent and Neovim

Readme

pi-nvim

Bridge between pi coding agent and Neovim. Run pi in one terminal pane and Neovim in another — send files, selections, and prompts from Neovim directly into your running pi session.

demo

How it works

The repo contains two components:

  1. Pi extension (extension.ts) — opens a unix socket when pi starts. External tools can send JSON messages to inject prompts into the active pi session.
  2. Neovim plugin (lua/pi-nvim/) — connects to that socket via libuv. Sends context from your editor to pi.

Discovery is automatic: the extension writes socket info to /tmp/pi-nvim-sockets/, and the Neovim plugin scans that directory, preferring sessions matching your cwd.

Install

Pi side

pi install npm:pi-nvim

Or add to ~/.pi/agent/settings.json:

{
  "packages": ["https://github.com/carderne/pi-nvim"]
}

Then /reload in pi.

Neovim side

With lazy.nvim:

{ "carderne/pi-nvim" }

Then in your config:

require("pi-nvim").setup()

Usage

Start pi in one terminal. Start Neovim in another. The pi extension automatically opens a socket on session start.

Commands

| Command | Description | |---|---| | :Pi | Open the Send to pi dialog (works in normal and visual mode) | | :PiSend | Type a prompt and send to pi | | :PiSendFile | Send current file path + prompt | | :PiSendSelection | Send visual selection + prompt | | :PiSendBuffer | Send entire buffer + prompt | | :PiPing | Check if pi is reachable | | :PiSessions | List/switch between running pi sessions |

Default keybindings

<leader>p is mapped to :Pi in both normal and visual mode by default.

The :Pi dialog

Opens a floating window in the center of the screen:

  • Shows the current file name (always sent)
  • If you had a visual selection, it shows the line range and sends the selected text
  • If no selection, you can press Tab to toggle sending the entire buffer
  • Type a prompt and press Enter to send (or just Enter with no prompt)
  • Press Esc or Ctrl-C to cancel

Additional keybindings

vim.keymap.set("n", "<leader>pp", ":PiSend<CR>")
vim.keymap.set("n", "<leader>pf", ":PiSendFile<CR>")
vim.keymap.set("v", "<leader>ps", ":PiSendSelection<CR>")
vim.keymap.set("n", "<leader>pb", ":PiSendBuffer<CR>")
vim.keymap.set("n", "<leader>pi", ":PiPing<CR>")

Protocol

The socket accepts newline-delimited JSON:

{"type": "prompt", "message": "your prompt here"}
{"type": "ping"}

Responses:

{"ok": true}
{"ok": true, "type": "pong"}
{"ok": false, "error": "..."}

This means you can also send prompts from any tool:

echo '{"type":"prompt","message":"hello"}' | socat - UNIX-CONNECT:/tmp/pi-nvim-sockets/<hash>.sock

License

MIT