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

indexes-of

v1.0.1

Published

line String/Array#indexOf but return all the indexes in an array

Downloads

15,873,274

Readme

npmd

distributed npm client.

synposis

An alternative npm client, based around a local replication of the npm metadata. (package.json & readmes are replicated for every package, but only tarballs that you have installed are replicated)

replicating data locally makes the client much smarter, and enables all manner of Mad Science.

sync

To begin, replicate the registry metadata. When this gets near 100% you can use the other commands.

npm install npmd -g
npmd --sync

You should leave the npmd service running in the background, this will make running other npmd commands much faster.

npmd will pull down npm metadata, and store it in a leveldb. this will be less than 200mb, including a full text index.

install

install a module. if the module's dependencies are in the cache, then npmd will install without making a single network round trip!

npmd install browserify --greedy

--greedy is optional, if enabled, the dependency tree is flattened as much as possible. so you have less duplication.

publish

publish a module locally. In a package directory, just do:

npmd publish

and your package version will be stashed into a queue for local use. You can npmd install yourpkg locally even if yourpkg isn't on the public npm yet. You can even have multiple versions of your package queued up locally.

To inspect your local package queue, do:

npmd queue

You can remove a package from your queue with:

npmd queue rm pkgname@version

To sync your local package queue with the public npm, you can run:

npmd queue sync

resolve

resolve all module versions required to install a given module. will write json to stdout in the same format as npm-shrinkwrap.

npmd resolve request

License

MIT