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 🙏

© 2024 – Pkg Stats / Ryan Hefner

rimraf-standalone

v2.6.1-7

Published

A deep deletion module for node (like `rm -rf`), as a single-file JS script

Downloads

809

Readme

Build Status

The UNIX command rm -rf for node.

Rimraf (rm -rf) as a standalone script

This is a fork of the original rimraf, which provides a standalone single-file script. The script is the result of bundling rimraf with its dependencies, using Rollup.

Why? Example #1: to clean node_modules

Many developers would like to use rimraf as part of a "clean" task which deletes all non-source control files in the project, including the node_modules directory. Unfortunately, this has two major downsides:

  • Must npm install to have rimraf available for cleaning.
  • On some platforms, rimraf of node_modules fails, because the execution of rimraf keeps files open/locked in the node_modules directory.

One workaround is to perform a global install of rimraf, but that violates the principle of a package including any needed development libraries in devDependencies, and breaks if rimraf is installed both globally and in the project.

For a more comprehensive workaround, rimraf-standalone provides rimraf-standalone.js which you can copy to the root of your project, commit in your project, and call from a package script.

If you just want to obtain the standalone script, you don't even need to install this package!

Rather, do something like this:

wget https://unpkg.com/rimraf-standalone/rimraf-standalone.js

Then set up your package script:

  "scripts": {
    "clean": "node rimraf-standalone.js node_modules"
  },

To clean:

npm run clean

How it was bundled

Creating this standalone bundle is a straightforward use of Rollup.js; see the package source files, particularly rollup.config.js, for details.

rimraf was written by Isaac Schlueter, and his name remains in the package.json author field.

This repackaging was done by Kyle Cordes at Oasis Digital.