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

@elianiva/pi-starship

v1.0.0

Published

Starship-style prompt for pi

Downloads

62

Readme

@elianiva/pi-starship

Starship-style prompt components for pi. This is a library package, not an auto-loading extension. See why This will NOT work outside of Pi's environment, which loads the files using jiti.

Installation

# or any other package manager of your choice
bun add @elianiva/pi-starship

Usage

Create your own extension in ~/.pi/extensions/my-extension/:

import type { ExtensionAPI } from "@mariozechner/pi-coding-agent";
import {
  StarshipEditor,
  createStarshipWidget,
  setupStarshipEvents,
} from "@elianiva/pi-starship";

export default function myExtension(pi: ExtensionAPI) {
  pi.on("session_start", async (_event, ctx) => {
    if (!ctx.hasUI) return;

    // Use the starship editor
    ctx.ui.setEditorComponent(
      (tui, theme, kb) => new StarshipEditor(tui, theme, kb, undefined, ctx)
    );

    // Add the info widget (shows cwd, git/jj branch, tokens, etc)
    createStarshipWidget(pi, ctx);
  });

  // Register event handlers for widget updates
  setupStarshipEvents(pi);
}

API

StarshipEditor

Custom editor class with a ❯ prompt prefix and suppressed borders.

new StarshipEditor(
  tui: TUI,
  editorTheme: EditorTheme,
  keybindings: KeybindingsManager,
  options?: EditorOptions,
  context?: ExtensionContext
)

createStarshipWidget(pi, ctx)

Initializes the info widget showing:

  • Current directory
  • Git/Jujutsu branch and commit
  • Model name
  • Thinking level
  • Token usage (input/output/cache)
  • Cost
  • Context window usage

setupStarshipEvents(pi)

Registers event handlers that update the widget:

  • session_switch - Refresh VCS info
  • agent_start/agent_end - Update stats
  • turn_end - Update after each turn
  • model_select - Update model display
  • user_bash - Debounced VCS refresh (after shell commands)

refreshVcs(cwd, callback?)

Manually refresh VCS info. Cached for 2 seconds.

getVcs()

Get current VCS cache state:

{
  info: {
    type: "git" | "jj",
    branch: string,
    commit: string,
    commitRest?: string,
    dirty: boolean
  } | null,
  time: number,
  cwd: string
}

Why a Library Package?

Extensibility: This is intentionally designed as a library you compose, not a ready-to-use extension. You can pick and choose which part you want, you might just want the editor, you might just want the info widget, or both!

No hard dependencies: This extension was made alongside my other extension, @elianiva/pi-ckers, which also overrides the editor, but I want to compose them and not have them have hard dependencies from one another.

Overrides editor: Since this wraps/replaces the editor component, it can't be an auto-loading extension because you may have other extension that already overrides the editor. The extension loading in Pi have no particular order, so you can't stack overriding editors. You can still use this extension without overriding the editor, you just won't get the minimal look that removes the borders and adds the ❯ prompt.

See how I use it in my configuration.

License

MIT