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

@ladbabynpm/picc-write

v0.1.1

Published

Claude Code style Write tool for pi — a faithful port of Claude Code's `Write` (create/update, read-first guard, structured diff).

Readme

picc-write

npm downloads

Claude Code style Write tool for pi — a faithful port of Claude Code's Write tool, overriding pi's built-in write.

Part of picc, a pi agent setup mirroring Claude Code's harness.

pi's built-in write is a thin fs.writeFile wrapper: input path (relative or absolute), no "must read first" guard, no create/update distinction, and a Successfully wrote N bytes message. This extension replicates Claude Code's Write: file_path (absolute) input, a session-scoped read-first guard, create-vs-update results with a structured diff, and faithful success messages.

Usage

Install via pi install npm:@ladbabynpm/picc-write.

Tool

  • Name: write (default; overrides pi's built-in write) or Write — configurable (see below).
  • Parameters: file_path (absolute, required), content (required).
  • Behavior:
    • New file — parent dirs are created automatically; returns File created successfully at: <path>.
    • Existing file — must have been read this session (any read tool), and must not have been modified since that read; returns The file <path> has been updated successfully. with a structured diff.
    • Writes with explicit LF handling (the model's sent line endings are respected as-is — no repo resampling).
  • Read-first guard: reads are observed from pi tool_result events for any read tool (read/Read), so it works whether the file was read with pi's built-in read or picc-read's Read. The map is cleared on session_start.

Configuration

| Setting | Where | Values | Default | |---|---|---|---| | toolName | config.json | "write" | "Write" | "write" | | PICC_WRITE_TOOL_NAME | env | "write" | "Write" | — | | PICC_WRITE_CONFIG_PATH | env | absolute path to a config.json | ~/.pi/agent/extensions/picc-write/config.json |

Precedence for the tool name: PICC_WRITE_TOOL_NAME env > config.json > "write".

What is omitted from the live source

No pi equivalent, so left out: permission checks (checkWritePermissionForTool), checkTeamMemSecrets, team-memory guards, skill discovery, fileHistory, LSP didChange/didSave, notifyVscodeFileUpdated, gitDiff, and analytics.

Development

npm install
npm run lint        # biome check
npm run typecheck   # tsc --noEmit
npm run test        # vitest run