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

@flowwright/plugin-std

v0.1.1

Published

FlowWright shared library — standard reusable steps (cleanWs, deleteDir, checkout, writeFile, stash).

Readme

@flowwright/plugin-std

The everyday workspace helpers you reach for (cleanWs, deleteDir, checkout, …) — real, typed imports from a versioned npm package instead of magic step names.

Every helper is a thin wrapper over @flowwright/core primitives, so each call is recorded into the execution-plan IR and shows up in flow explain, the graph, and CI export. Nothing happens behind your back.

Usage

Call the helpers inside a stage body:

import { pipeline, stage } from "@flowwright/core";
import { cleanWs, deleteDir, checkout } from "@flowwright/plugin-std";

export default pipeline({
  name: "build",
  stages: [
    stage("Checkout", async () => {
      await checkout("[email protected]:acme/app.git", { ref: "main", depth: 1 });
    }),
    stage("Build", { needs: ["checkout"], run: async () => { /* … */ } }),
  ],
  // run cleanup no matter what — see the post/always lifecycle
  post: { always: async () => { await cleanWs(); } },
});

Helpers

| Helper | What it does | |---|---| | cleanWs() | Empties the working directory (keeps the dir, removes all entries incl. dotfiles). | | deleteDir(path) | rm -rf a path. | | checkout(url, { ref?, dir?, depth?, submodules?, fetchTags? }) | Clone a repo, then optionally check out a ref. Re-exported from @flowwright/plugin-git. | | gitCheckout(ref) | git checkout <ref> in the current tree. Re-exported from @flowwright/plugin-git. | | gitClone(url, dir?) | git clone into dir. Re-exported from @flowwright/plugin-git. |