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

arum-aruff

v0.0.2

Published

helps with removing dead components

Downloads

3

Readme

ARUM-ARUFF

Maintenance status published on npm!
Known Vulnerabilities Testing Status Test Coverage Maintainability


WHAT IT DO:

Builds a tree of your app, and tells you what components/packages should/might be easiest to delete!

HOW TO RUN IT:

  npm i -g arum-aruff
  cd SOME_PROJECT_FOLDER
  arum-aruff

DEV NOTES:

  • Tests are a nightmare. fs mocking with generally non-serial ava means any test failures will look horrifying and nonsensical. You'll never be able to tell what's wrong for the most part. Just assume any changes that start failing are the latest thing you've done.

TODO:

  1. fsPromises fail to work well with package.json files, refactoring when mock-fs works correctly would be nice.
  2. package.json deps that aren't imported anywhere reporting
  3. CI testing & one19/project-status integrations
  4. a happy little svg icon of a pupper and a glass of rum
  5. export strength mapping
  6. tracing imports & exports from file to function name
  7. Baller d3 web
  8. _size reporting for tree/single-file lines of code/bits
  9. parsing test configs or allowing to have a -i input to allow ignoring any regex