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-nmless

v1.2.17

Published

CLI for deleting node_modules from an old projects

Downloads

37

Readme

Remove node_modules cli

climate npm license commit

This is the CLI that allows removing unused by days count node_modules. Zero dependencies, ~100% test coverage. ✨

Table of Contents

Installation and Usage

Prerequisites: Node.js (^12.22.0, ^14.17.0, or >=16.0.0) built with SSL support. (If you are using an official Node.js distribution, SSL is always built in.)

You can install using npm:

npm i -g rm-nmless

After that, you can execute by the command line using:

rm-nm $COMMAND$ $PATH$ $DAYS$

See the Arguments for more information.

Arguments

Allowed methods:

check - check and print folders which should be deleted. (default method)

rm-nm check

execute - delete folders and print deleted folders.

rm-nm execute

Allowed arguments:

path - path to folder with projects. See Structure and Examples for more information.

--path=$VALUE$

days - how many days passed after the last editing. Any number value, if that will be zero it equal to all the time. (Default 14 days)

--days=$VALUE$

verbose - where parse ended, print additional information about a files

--v

or

--verbose

Example Structure

projects <-- path to this folder
│
└───sample_proj_1
│   │   node_modules <-- will be deleted
│   │   ...
└───sample_proj_2
│   │   node_modules <-- will be deleted
│   │   ...
└───sample_proj_3
│   │   node_modules <-- will be deleted
│   │   ...

Example Commands

Default usage:

rm-nm check --path=../../ --days=7
rm-nm execute --path=../../ --days=7

or without path:

rm-nm check <- would be used current  folder
  • path also can be like this:
rm-nm check --path=.

or this:

rm-nm check --path=~ <-- parse user directory

or event this:

rm-nm check --path=/ <-- parse root directory
  • also you can use like this to check:
rm-nm --path=../../ --days=7
  • you can also use without days(default 14d), like this:
rm-nm check --path=../../
rm-nm execute --path=../../
  • days = 0, says that the last changed irrelevant:
rm-nm --path=../../ --days=0 <-- will be deleted all node_modules which will be found

Future Goals

  • Providing more information about projects.

Contribution

Show your ❤️ and support by giving a ⭐. Any suggestions, issues or PR's are welcome!