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

@crossplatformai/clean

v0.1.0-next.0

Published

Cross-platform cleanup tooling for CrossPlatform.ai workspaces.

Downloads

634

Readme

@crossplatformai/clean

Cross-platform cleanup utilities for CrossPlatform.ai workspaces.

Overview

@crossplatformai/clean provides a small programmatic API and CLI for removing common build artifacts, caches, and dependency directories without relying on shell-specific rm commands.

It supports three cleanup modes:

  • explicit path cleanup
  • glob pattern cleanup
  • repository root cleanup for Turbo and pnpm workspaces

Installation

Install the package as a development dependency in a workspace that needs shared cleanup scripts:

pnpm add -D @crossplatformai/clean

CLI Usage

crossplatformai-clean --root
crossplatformai-clean --root --dry-run
crossplatformai-clean --root --keep-node-modules
crossplatformai-clean --root --verbose
crossplatformai-clean dist .turbo node_modules/.cache
crossplatformai-clean --pattern "**/.eslintcache" "**/*.tsbuildinfo"

Options

| Option | Description | | --------------------- | -------------------------------------------------------------------- | | --root | Clean the detected repo root using the built-in workspace patterns | | --pattern | Treat the remaining arguments as glob patterns | | --dry-run | Report what would be removed without deleting anything | | --keep-node-modules | Skip root and nested node_modules deletion during --root cleanup | | --verbose | Report each cleaned, skipped, or missing path | | --help, -h | Show help |

Programmatic Usage

import {
  cleanPaths,
  cleanPatterns,
  cleanRoot,
  findRepoRoot,
} from '@crossplatformai/clean';

const repoRoot = await findRepoRoot(process.cwd());

await cleanPaths(['dist', '.turbo'], { cwd: repoRoot });
await cleanPatterns(['**/.eslintcache', '**/*.tsbuildinfo'], { cwd: repoRoot });
await cleanRoot({ cwd: repoRoot, dryRun: true });

Root Cleanup Targets

cleanRoot() removes these targets by default:

  • .turbo
  • **/.turbo
  • node_modules/.cache
  • **/.eslintcache
  • **/*.tsbuildinfo
  • **/dist
  • **/.next
  • **/out excluding **/android/**
  • **/coverage
  • **/.vitest-cache
  • **/node_modules

During CLI --root cleanup, node_modules contents are removed while the active @crossplatformai/clean package, its launcher shim, and its runtime dependencies are preserved so the cleanup process can finish reliably. Nested workspace node_modules directories are still removed.

Use --keep-node-modules or { keepNodeModules: true } to keep dependency directories.

Notes

  • Missing paths are treated as a successful no-op.
  • Repo root discovery walks upward and requires either turbo.json or pnpm-workspace.yaml.
  • A best-effort pnpm turbo clean run is attempted during root cleanup, but failures are non-fatal.