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

@squiz/xaccel-testing-helpers

v1.13.0-alpha.7

Published

These are files that are used to help with Jest tests.

Downloads

482

Readme

Jest Helpers

These are files that are used to help with Jest tests.

jest.config.cjs

The jest config is the global jest config file, this file is imported into the jest.config.cjs in the root of the project repo and serves as the base for all jest configs.

This can be overwritten via putting a jest.config.cjs file in your current package. The most likely time that this will need to happen is for test coverage percentage changes, or for testing a server side only package etc where the config is expected to be different.

Coverage

By default the global coverage threshold has been set at 100%, this can be addressed on a case by case basis if it needs to be lowered because of untestable code, however the preferred method is to write testable code.

To overwrite coverage for a particular module or file, you should place a jest.config.cjs file in the modules root folder, add this package (@plug-and-play/base-component-jest-helpers) as a dev dependency, and then spread the config and update the specific file thresholds as needed.

E.g

const jestConfig = require('@plug-and-play/base-component-jest-helpers');

module.exports = {
    ...jestConfig,
    coverageThreshold: {
        './src': {
            branches: 0,
            functions: 0,
            lines: 0,
            statements: 0,
        },
    },
};