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

rm-safe

v0.0.4

Published

Use the `rm` shell command, safely.

Downloads

9

Readme

rm-safe ✔️

Why 'adjust' rm?

👉 The rm command is a footgun.

If you're like me, you've shot yourself in the foot too many times using the standard rm shell command. This CLI module is a simple attempt at adding a layer of safety around rm, while still fulfilling its intended purpose.

rm has no built in safety. The files you target get unlinked, the metadata is removed, and it's just gone. In other words: if you delete something, its permanently deleted. If you're confident you'll use it correctly all the time, then more power to you, I only hope this module might ease your conscience more if you're not.

What's different?

safe-rm has two opinions:

1️⃣ A backup of the files you delete should be temporarily stored in a common /temp directory, so that you can recover something if you did not intend to delete it.

2️⃣ A last-ditch confirmation dialogue should happen whenever you use the -r, -rf, or -Rf flags. This way

Installation

  1. Run $npm install -g rm-safe

  2. If you don't have one already, add a new local ~/temp directory to ensure the system always knows where to eventually delete your backup files. safe-rm will add one for you when you first run it if it doesn't exist, but you'll still need to add this line to your local shell configuration file (eg. ~/.bash_profile, ~/.bashrc, etc): export TMPDIR=~/temp

  3. Add an alias for the rm command in your shell configuration file: alias rm="rm-safe" (Note: this will only work if rm-safe has been installed globally).

Use

  • If you added the alias, you can now use rm-safe just like you're used to with rm.
  • If you'd rather not add an alias, you can just run $rm-safe command from your terminal.
  • rm-safe also supports the use of standard wildcards (eg. rm my-directory/*, rm *.txt, *example*, etc).

License: ISC