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

js-explorer

v1.1.7

Published

A terminal-based resource to help you find js methods without digging through the docs

Downloads

20

Readme

JavaScript Explorer

Find the method you need without digging through the docs! ✨

When I was first learning array and object methods, I spent a lot of time digging through the docs to find the appropriate one, and I had to search one by one. I made this resource to help people find the correct object method a bit more naturally. You can narrow down what you want to do and explore until you find what's most useful to you.

js-explorer-demo

It's been 4 years since I released the Array and Object Explorers as tools for the community. I realized it interrupts flow state to have to go to a web app to use them, so I thought a command line tool might be a better developer experience.

Usage

I recommend installing the tool globally, so that you can make use of it no matter what project you're working on, but you can take out -g flag if you want to use it in particular projects instead:

npm i -g js-explorer

Note: You may need to run sudo before this command- sudo npm i -g js-explorer

Then, to kick off the explorer, type:

jsexplorer

You will be guided through prompts to find your method!

It will also allow you to save the entry at the end (optional.)

Other commands

jsexplorer plain

Runs the tool without asking to save at the end.

jsexplorer -p

Same as above, aliased p for plain.

lookup [string to look up]

If you save an entry, you can run lookup and the string to find that entry and print it.

For example, let's say you ran the explorer and at the end when it prompts you to save, you saved Array.slice() as "That one I always mix up with the other one!" You would type lookup That one I always mix up with the other one!

A more simple example might be homeslice, in which case you would run lookup homeslice.

clearlookup

Clears all saved jsexplorer entries.

More information on the project

I realize that there are about a million ways that this resource can be set up, and some of the taxonomy is necessarily opinionated. I tried to focus on what I thought would have helped me learn the best, rather than industry standard delineations. If that style of learning suits you better, that's great! This resource is not set up that way. Please keep in mind that this is not meant to be as comprehensive or a replacement for full documentation, which is why the MDN docs are linked to in each method.

I based most of the longer descriptions off of the MDN documentation, altering it slightly where I felt the description was not as beginner-friendly as it could be. The examples were kept as simple as humanly possible for the purpose of scanning with the least cognitive load, you may need extra details provided in the MDN documentation for every possible usage.

Enjoy! 🌮