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

hubble-x

v0.3.6

Published

A visual regression testing tool for React components

Downloads

5

Readme

hubble

A visual regression testing tool for React components

Installation

npm i hubble-x --save-dev

Usage

Create a folder named hubble-tests in the root of your React app. This is where you will keep your tests. Make sure your tests end with the .test.js extension. Example repository structure:

your-react-app/
├── node_modules/
│   └── hubble-x/
└── hubble-tests/
    └── your-tests.test.js

An example test file:

// Accordion.test.js
import React from 'react';
import hubble from 'hubble-x';

import Accordion from '../components/Accordion';

hubble.testGroup('Accordion')
  .add('expanded', () => (
    <Accordion label="Hello" isExpanded="true">
      Some content
    </Accordion>
  ))
  .add('not expanded', () => (
    <Accordion label="Hello" isExpanded="false">
      Some content
    </Accordion>
  ), {x:0, y:0, width:800, height:200});

Run your tests: $ npx hubble

View the report: $ npx hubble report

Screenshots

Terminal output:

presi_gif

HTML report:

API

.testGroup(groupName)

  • groupName <string> The name of this test group.

.add(testName, reactFn, [clip])

  • testName <string> The name of the test to be added.
  • reactFn <function()> A function which returns a react component.
  • clip <Object> An object which specifies clipping region of the page. Should have the following fields:
    • x <number> x-coordinate of top-left corner of clip area.
    • y <number> y-coordinate of top-left corner of clip area.
    • width <number> width of clipping area.
    • height <number> height of clipping area.
    • default: {x: 0, y: 0, width: 800, height: 600}

CLI

Run all tests: $ npx hubble

Run a group of tests: $ npx hubble GroupName

Run a single test: $ npx hubble GroupName/TestName

Update the "expected" image for tests: $ npx hubble --update

View HTML report: $ npx hubble report