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

what-i-actually-need

v1.0.5

Published

![logo](https://i.imgur.com/Zc5otUj.png) Scans your code to find all the require() to tell you what you actually need for the node project. Uses a single file as the starting point then does depth first search. Optional -- It can also update your package.

Downloads

3

Readme

logo Scans your code to find all the require() to tell you what you actually need for the node project. Uses a single file as the starting point then does depth first search. Optional -- It can also update your package.json after to only include the needed modules under dependencies.

Usage

install

$ npm i what-i-actually-need -g

run

Run the following in a node project. By default it uses index.js as the entry point to start the scan.

$ what-i-actually-need

example output:

-- Running What-I-Actually-Need ---

index.js
--> node-sass
--> css-modules-require-hook
--> babel-register

server.js
--> nconf
--> log4js
--> http
--> https
--> fs
--> path

--------------------
12 dependencies are actually needed. There are currently 51 dependencies in package.json.
--------------------

Run the 'what-i-actually-need' command with '--run' flag to update package.json.

Options

--entry (Default: index.js)

Entry point of your node based project, it will start the scan from this file.

--run

To update the package.json dependencies after the scan is complete.

--help

See the usage docs