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

depsane

v0.1.0

Published

Checks for missing dependencies based on code reachable from the main entrypoint specified in package.json

Downloads

36

Readme

depsane

Test application

Checks for missing dependencies based on code reachable from the main entrypoint specified in package.json (defaults: index.js). Furthermore: if a bin-object is specified in package.json all code reachable from those files will also be included.

depsane is focused on determining which dependencies that should be present specifically in dependencies and devDependencies. It classifies a dependency found in devDependencies used in the main code path as missing, and a dependency only used as a devDependency but that is specified in dependencies is considered missing.

This solves the problem where an application works fine locally and during testing but fails once deployed as the deployed version will only be installed with its' dependencies but during testing and development both devDependencies and dependencies are installed.

There is also some experimental heuristics implemented to determine if mocha or eslint and their associated plugins are used as devDependencies or not.

Installation

npm install --save-dev depsane

Usage

npx depsane [directory] [arguments]

Prints missing dependencies and unused dependencies.

Exits with code 0 if no missing or unused dependencies are found and 1 otherwise.

The directory defaults to the current directory.

All of the arguments are optional:

--ignore-dirs: comma-separated list of dirs to ignore.

--ignores: comma-separated list of dependencies to ignore, supports wildcards (i.e. "eslint*" will ignore all dependencies that starts with eslint).

Changelog

Can be found here.

License

Released under the MIT license.