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

@lg-tools/test

v0.4.10

Published

Jest setup & config for LeafyGreen repositories

Downloads

61

Readme

@lg-tools/test

Shared test config & scripts for LeafyGreen repositories.

Usage

It's best not to use this as a standalone package, but use it as part of @lg-tools/cli instead.

To run tests using the shared config, use the lg cli:

> lg test

Options

To see all options for this command run:

> lg test --help

Extending & overriding the shared config

To extend/override the shared config (located in @lg-tools/test/config), create a jest.config.js file at the root of the repository, and extend the default config with the code below:

// ./jest.config.js
const jestConfig = require('@lg-tools/test/config/js.config.js');

module.exports = {
  ...jestConfig,
  // extend your jest config here
};

You can also pass a --config option to the test command:

> lg test --config ./path/to/config

Testing in React 17

In CI we test our components using React 17.

To do this manually, first run the init script in order to install the specific testing dependencies needed for React 17. (yarn init17 from the repo root)

> yarn init17

Next, run your tests with the --react17 flag. This ensures that the tests are run with specific Jest config for React 17.

> yarn test --react17

To go back to the default version of React you'll need to clear your packages and re-build:

> yarn clean:modules && yarn run init