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

@pocketjs/cli

v0.11.0

Published

The PocketJS CLI — manifest-first handheld builds, app scaffolding, and pinned native toolchain setup.

Readme

@pocketjs/cli

The PocketJS toolchain CLI — doctor/setup for the bun + Rust + PSP toolchain (flutter-doctor style), manifest-first app scaffolding, build/run passthrough for PSP and PS Vita, an isolated Nokia E7 / Symbian development toolchain, and an Apple iOS flow that stages guests into a NativeScript shell and launches them on the simulator.

npm install -g @pocketjs/cli

pocket doctor            # diagnose Bun / pinned Rust + PSP toolchain
pocket setup             # run PocketJS's pinned, idempotent bootstrap
pocket create my-app     # scaffold apps/my-app with pocket.json v2
pocket check --target psp --manifest apps/my-app/pocket.json
pocket compile --target psp --manifest apps/my-app/pocket.json
pocket build --target psp --manifest apps/my-app/pocket.json -- --release
pocket build --target vita --manifest apps/my-app/pocket.json -- --release
pocket play vita hero    # build, install and launch a stock demo in Vita3K
pocket dev my-app-main   # build + serve in the browser
pocket psp my-app        # build the PSP EBOOT
pocket vita my-app       # build the PS Vita VPK
pocket symbian doctor --device
pocket symbian doctor --coda-usb
pocket symbian setup --yes
pocket symbian build probe
pocket symbian deploy dist/symbian/pocketjs-e7-probe.sis
pocket symbian coda usb
pocket symbian coda usb launch <executable.exe>
pocket ios doctor
pocket ios setup
pocket ios play nsengine     # NativeScript shell on the arm64 iOS simulator
pocket play ios nsengine     # the same flow through the play front door
pocket hw my-app         # build + run on a real PSP over PSPLINK
pocket psplink           # interactive multi-app switcher on a real PSP
pocket devtools my-app   # DevTools panel + USB debug bridge, one command
pocket tape replay …     # record / replay / inspect input tapes headlessly

Commands run inside a PocketJS checkout (the CLI finds it by walking up from the current directory):

git clone https://github.com/pocket-stack/pocketjs
cd pocketjs && bun install
pocket doctor

check, compile, and build delegate to PocketJS's canonical manifest resolver. pocket.json owns the framework, entry, output, viewport and API requirements; the target backend consumes the resulting build plan. Arguments after -- go to the selected PSP or Vita backend. The low-level dev, psp, vita, hw, psplink, devtools, and tape commands remain available for framework demos and host development.

Only Node ≥ 18 is required for the CLI itself; everything it diagnoses or installs is for building PocketJS apps. See the repository and pocketjs.dev for the framework docs.

pocket setup installs the exact toolchain described by the CLI's bundled psp-toolchain.json into the shared pocket-stack cache. PSPLINK is diagnosed as an optional real-hardware hot-reload tool; it is not required to build a PSP EBOOT.