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-hyperclick-core

v1.1.0

Published

This package provides the tools for [js-hyperclick][js-hyperclick] to scan JS files for variables, imports, exports, and to locate imported modules.

Downloads

9

Readme

js-hyperclick-core

This package provides the tools for js-hyperclick to scan JS files for variables, imports, exports, and to locate imported modules.

Why split this into an npm package?

Atom's testing process doesn't work for me. The command Run Package Specs opens a new window every time instead of just reusing the last spec window. You can reuse the window, but you have to either click a button in that window or switch to the spec window and ctrl+alt+r to reload the window.

Since this package uses Jest, I can run it with --watchAll --coverage and monitor my tests without ever leaving Atom or having to use the mouse.