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

lazyspec

v2.1.2

Published

Generate minimal unit tests automatically

Downloads

24

Readme

LazySpec

Automatically generate minimal spec files for Javascript modules. Works well with Jest snapshots to make painless tests. For example, given a test file src/components/Button.jsx,

import React from 'react';

class Button extends React.Component {
  static propTypes = {
    level: React.PropTypes.oneOf([
      'primary', 'secondary', 'tertiary', 'quaternary', 'text', 'icon',
    ]),
    disabled: React.PropTypes.bool,
    label: React.PropTypes.string.isRequired,
    height: React.PropTypes.number,
    children: React.PropTypes.element.isRequired,
  };

  render() {
    return (
      <button disabled={this.props.disabled}>
        <b>{this.props.label}</b>
      </button>
    );
  }
}

export default Button;

it will generate src/components/__tests__/Button-test.js:

/* @lazyspec (remove to manage manually) */
/* eslint-disable */
import Button from '../Button.js';

import React from 'react';
import renderer from 'react-test-renderer';

describe('Button', () => {
  it('exists', () => {
    expect(Button).toBeTruthy();
  });

  it('renders', () => {
    const comp = <Button children="mockElement" label="mockString" />;
    const tree = renderer.create(comp).toJSON();
    expect(tree).toMatchSnapshot();
  });
});

Usage

npm install -g lazyspec
lazyspec path/to/fileOrDir

For every dir in the list, it will glob all the .js and .jsx .js and add them.

For each file, it will generate a spec and the __tests__ dir if necessary. So far it only supports the Jest style layout but PRs for other test runners and layouts are welcomed!

In dev you can do, ./src/cli.js path/to/fileOrDir.

Known Issues

  • Required props of functional stateless components aren't detected

  • Custom proptypes are never interpreted as required (e.g. message: MessageInterfacePropType.isRequired)

  • Fails when more than one component is exported from a module. react-docgen now has findAllExportedComponentDefinitions, but we don't use it because modules often export a HOC and its base component so it would be redundant. Eventually this tool could detect which is the HOC and omit it.