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

grunt-clean-npm

v0.0.4

Published

Cleans node_module for the local project when there was any changes in package.json dependencies or devDependencies

Downloads

3

Readme

grunt-clean-npm

Cleans node_module for the local project when there was any changes in package.json dependencies or devDependencies. As npm has issues with resolving dependencies when you already downloaded some old versions, it is better to remove node_modules. But to do it each time is not a solution, as to download all of your dependencies when you have a few of them could take a time, so better to be a bit smarter and do it only when you really need it.

Setup

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-clean-npm --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-clean-npm');

Using grunt-clean-npm

It consists of 2 tasks, first one removes the node_modules if md5 wasn't generated yet or md5 is different.

grunt remove-node-modules

the second one generates the hash inside of node_modules.

grunt generate-hash

So my advice to use it in the next order:

grunt remove-node-modules
grunt npm-install
grunt generate-hash

How it works

Module checks whether the dependencies or devDependencies in package.json are changed, and if so removes node_modules folder.