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

@patimweb/pi-nodejs-bestpractices

v0.3.1

Published

Node.js best practices for the Pi coding agent — Matteo Collina's `node` skill, vendored 1:1 from mcollina/skills (MIT). TypeScript type-stripping, async patterns, error handling, streams, performance, profiling, testing, and more.

Downloads

434

Readme

@patimweb/pi-nodejs-bestpractices

Node.js best practices for the Pi coding agent, shipping Matteo Collina's node skill — vendored 1:1 from mcollina/skills.

Attribution: skill content is © 2026 Matteo Collina, MIT License (see skills/node/LICENSE). Packaging by Patrick Weppelmann.

What's Included

| Resource | Path | Purpose | |----------|------|---------| | Skill | skills/node/SKILL.md | Collina's node skill — Node.js best practices (TypeScript-first) | | Rules | skills/node/rules/*.md | 14 rules: async patterns, error handling, streams, caching, performance, profiling, logging, modules, testing, TypeScript, graceful shutdown, environment, flaky tests, stuck processes | | Assets | skills/node/rules/assets/*.ts | Graceful-server reference implementation + test |

Install

From npm

pi install npm:@patimweb/pi-nodejs-bestpractices

From a git repo

pi install git:github.com/Smotherer007/[email protected]

Try without installing

pi -e ./

Usage

The node skill loads automatically for Node.js questions, or force it explicitly:

/skill:node

Development

npm install
npm test        # validates skill frontmatter (node:test)

Release

Releases are automated via semantic-release (.github/workflows/release.yml). Pushing a conventional commit (feat:/fix:) to main triggers: version bump → npm publish → GitHub release + tag.

License

MIT. Skill content © Matteo Collina (MIT) — see skills/node/LICENSE.