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

ivh-react-component-scripts

v2.1.8

Published

Dependencies for components build with generator-ivh-react-component

Downloads

9

Readme

IVH React Component Scripts

This module declares dependencies required for components built with the ivh-react-component yeoman generator and also provides common scripts for developing those components.

Why? Mostly because it's tedious to manage and synchronize large dependency lists between many packages. We also aim to keep package versions consistent with those used by react-scripts.

This lets us have a single package version to bump and easily separates shared dependencies vs those required for an individual module.

We currently support scripts for...

Building

Add ivh-react-component-scripts build as an npm script in your package.json, e.g.:

// package.json
{
  "name": "foo-package",
  "scripts": {
    "build": "ivh-react-component-scripts build"
  }
}

Then simply run npm run build or yarn build.

Testing

Add ivh-react-component-scripts test as an npm script, e.g.:

// package.json
{
  "name": "foo-package",
  "scripts": {
    "test": "ivh-react-component-scripts test"
  }
}

Then simpy run npm test or yarn test. Note that, unlike react-scripts, we don't "watch" your source files by default. Use the jest paramters --watch or --watchAll to enable watching.

You may place a test setup file at src/setup-tests.js if you need to run a script to configure or setup the testing framework before each test - e.g. to register an adapter for Enzyme. See the jest docs for more information.