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

@automated/automated

v0.100.0

Published

Use-case-oriented testing

Downloads

5

Readme

Automated ⚙️

Automated is a test framework designed to simplify testing by standardizing.

With a few lines of code here’s what you get out of the box:

  1. Multiple viewport visual regression coverage
  2. Jest unit tests (via snapshots)
  3. Code coverage (can persist to CI)
  4. Storybook artifacts (can persist to CI)
  5. Isolated component development environment (Storybook)

Installation

__automated.tsx

Quick start

  1. Go to one of your components and let’s say the component is named “Foo”
  2. Put it in a folder called “foo” with the component file named index.tsx
  3. Make the component the default export
  4. Add a sibling file named __automated.tsx, with the following contents
import Component from '.';

export default {
  Component,
  dirname: __dirname,
};
  1. Then run yarn automated init (You’ll see some files added).
  2. Now you can run yarn automated storybook to see it in an isolated dev environment
  3. Open another terminal and run yarn automated jest to generate snapshots and visual regression tests.

Examples

  1. Least content example
  2. More robust

API

__automated.tsx contents

export default {
  // [required] the subject React component
  Component,

  // [required] this supports automatic naming
  dirname: __dirname,

  // an array of use-cases
  useCases,
};

Contributing

# in one terminal
yarn nps dev

# in another
cd example && AUTOMATED_DEVELOPMENT=true yarn automated jest