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

react-project-graph

v1.0.0

Published

Creates a VisJS map of react components to visualize component and file dependencies

Downloads

10

Readme

#React-Project-Graph Hobby project to create a VISNetwork compatible map of react imported components and files used inside the application.

Current Version

The current version is very basic, so use with caution. It's possible to specify a root folder and get a .txt file with the DOT String in it.

The DOT string can then be imported into whatever mapping tool your have laying around, I prefer VisJS to load up the file and display it inside the browser.

Based on the project size that is scanned, the file might take a while to load in the current version.

Upcoming Ideas

A few ideas I have at the moment is adding support to detect:

  1. Mark unused imports with a red line
  2. Mark completly unused files, even when imported with a red node
  3. Nodes that are imported more than 5 times should be blue
  4. Nodes that have more than 10 imports should be green
  5. Mark nodes pink that have mismatching exports/filesnames

How to use

	node index.js -p <path to src in your react app>

The dot string will the written to dotstring.txt There is an index.html that has visjs-network setup to load the dotstring by default. I use it with

	python -m SimpleHTTPServer