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 🙏

© 2026 – Pkg Stats / Ryan Hefner

salazar

v1.4.0

Published

### Salazar is still under development, optimizations are being implemented. Stay tuned for further updates!

Readme

Salazar

Salazar is still under development, optimizations are being implemented. Stay tuned for further updates!

A UI focused library for test driven development.

Setup

Salazar has been designed so that you can easily drop the library into test scripts you've already written. We recommend you install Salazar via npm:

npm install salazar

Usage

Salazar relies on your description in your tests to connect UI snapshotting with corresponding unit tests. The "description" key in the object you pass to Salazar should be the exact string used for the describe used in the parent test.

...
describe("Enter Valid Email", function() {
  it("User enters email in user-email field", function() {
    expect(shallow(<LoginPanel />).contains(<input id="user-email" value="[email protected]" />)).to.equal(true);
    Salazar.run({
      progression: "successful login",
      description: "Enter Valid Email",
      element: "#user-email",
      action: "value",
      text: "[email protected]",
      png: "validemail1"
    });
    ...

From there, the library will compound objects in a given progression (i.e. a narrative for a given test) to ensure that preceding actions are taken leading up to a given snapshot:

describe("Initial UI State", function() {
  it("Interface Loads", function() {
    expect(shallow(<LoginPanel />).contains(<div className="login-panel" />)).to.equal(true);
    Salazar.run({
    	progression: "successful login",
    	description: "Initial UI State",
    	element: "",
    	action: "",
    	text: "",
		png: "loads1",
    });

    describe("Enter Valid Email", function() {
    	it("User enters email in user-email field", function() {
		    expect(shallow(<LoginPanel />).contains(<input id="user-email" value="[email protected]" />)).to.equal(true);
        //previous object sent in this progression will be processed before snapshot for this call is made
        //since it is nested in the same progression
        Salazar.run({
        	progression: "successful login",
		      description: "Enter Valid Email",
		    	element: "#user-email",
		    	action: "value"
		    	text: "[email protected]"
				png: "validemail2"
		    });

Visualization Tool

We're in the process of developing a more robust visualization tool but in the meantime you can use our progressions scrubber. Salazar will generate a narrative object in progressions.json. Configure your path for this file to be generated in the root of the visualizer directory. All of your narratives will be automatically organized by the "progression" key, making it easy to spot where your UI may not be behaving correctly even when corresponding unit tests might be passing.