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 🙏

© 2025 – Pkg Stats / Ryan Hefner

pureye

v0.1.0

Published

Source and test files watcher that runs your tests as you code, giving you instant feedback.

Downloads

5

Readme

Pureye

Test runners and continuous integration tools are fine for checking your overall coverage and ensure that no unexpected changes are introduced to the codebase. However, they are not quite convenient for the daily work, as the feedback loop for source code changes is relatively long. Pureye is a simple file watcher whose purpose is to provide you with immediate feedback over the updates you do on your code.

It works by observing your project's files by pairs. Imagine you have a file add.js with the following content:

const add = (a, b) => a + b

You might keep a battery of tests for it in a file add.test.js; you could start by:

assert('2 plus 2 should be 4', () => add(2, 2) === 4)

Whenever you change either add.js or add.test.js, both will be joined together and evaluated. You will see the results in the terminal in the blink of an eye.

As shown in the example, to write the tests a global function assert(message, assertion) is available. It accepts a description of the test as the first argument and a boolean-returning function as the second argument. If the assertion function returns true, the test will be considered passed, whereas if it returns false, we will say the test failed.

To start using the tool, place yourself at the root of your project and run the command. No arguments are needed, as the tool will try to figure out your project's conventions automatically, but you may configure some parameters through a 'pureye.json' file placed on the root of your project. You can see an example of it in the examples directory.

At the current stage, the tool is quite limited, only supporting pure functions. It would be a good idea for future development to extend it to support a wider variety of execution environments, covering both client- and server-side needs.