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

dependencies_analyzer

v1.0.7

Published

Analyzing dependences among Node.js modules. Given a Node.js app, the goal of this Analyzer is to automatically detect modules that remain unused or underused.

Downloads

8

Readme

This analyzer only supports modules which depend on Mocha as a test framework. So, /test folder which contains mocha-test-cases must be in the module directory.

Please note that analyzer needs two modules as input i.e. dependent module and dependency module. A dependent module is what the user is interested in knowing to what extend actually this module depends on (uses) dependency module.

to run: npm run build npm run start or node run.js

Note: make sure that you have run [npm install] inside the dependent module before its analyzing.

To run the each analyzer separately : Dynamic Analyzing: node ./node_modules/jalangi2/src/js/commands/jalangi.js --inlineIID --inlineSource --analysis ./x_analysis.js [dependent.js] -x [dependent_module directory] -y [dependency directory]

Static Analyzing: node node ./static_analyzer.js -x [dependent_module] -y [dependency_module directory] --api [dependency_object_name exactly as it is in dependent code]

// in order to run mongoose-validator test suite properly, mongodb process should be up and running of localhost and default port