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

@dbarrett24/jest-config

v1.0.0

Published

Shared Jest configuration for React/Next.js applications

Readme

@yourname/jest-config

Shared Jest configuration for React/Next.js applications with 90%+ coverage thresholds.

Installation

pnpm add -D @yourname/jest-config jest @testing-library/react @testing-library/jest-dom @testing-library/user-event

Usage

Create jest.config.js in your project root:

const baseConfig = require('@yourname/jest-config');

module.exports = {
    ...baseConfig,
    // Override or extend as needed
};

Setup Files

Create testing/setupTests.ts:

import '@testing-library/jest-dom';

// Add any global test setup here

Create mock files:

// testing/__mocks__/styleMock.js
module.exports = {};

// testing/__mocks__/fileMock.js
module.exports = 'test-file-stub';

Features

Automatic Mock Clearing

// ✅ Mocks automatically cleared between tests
beforeEach(() => {
    // No need for jest.clearAllMocks()
});

Path Aliases

// Use @/* imports in tests
import { MyComponent } from '@/components/MyComponent';

Coverage Thresholds

  • 90% minimum across all metrics (branches, functions, lines, statements)
  • Coverage collected from src/ directory
  • Excludes stories, tests, and mocks

Test Environment

  • jsdom for DOM testing
  • React Testing Library setup
  • jest-dom matchers included

Scripts

Add to your package.json:

{
  "scripts": {
    "test": "jest",
    "test:watch": "jest --watch",
    "test:coverage": "jest --coverage",
    "test:update": "jest -u"
  }
}

Customization

Adjust Coverage Thresholds

const baseConfig = require('@yourname/jest-config');

module.exports = {
    ...baseConfig,
    coverageThreshold: {
        global: {
            branches: 85,
            functions: 85,
            lines: 85,
            statements: 85,
        },
    },
};

Add Custom Module Mappings

const baseConfig = require('@yourname/jest-config');

module.exports = {
    ...baseConfig,
    moduleNameMapper: {
        ...baseConfig.moduleNameMapper,
        '^@components/(.*)$': '<rootDir>/src/components/$1',
    },
};

Exclude Files from Coverage

const baseConfig = require('@yourname/jest-config');

module.exports = {
    ...baseConfig,
    collectCoverageFrom: [
        ...baseConfig.collectCoverageFrom,
        '!src/generated/**',
    ],
};

Testing Best Practices

Use React Testing Library

import { render, screen, userEvent } from '@testing-library/react';

it('handles user interaction', async () => {
    const user = userEvent.setup();
    render(<MyComponent />);
    
    await user.click(screen.getByRole('button'));
    
    expect(screen.getByText('Success')).toBeVisible();
});

Prefer .toBeVisible()

// ✅ Good - tests actual visibility
expect(screen.getByText('Hello')).toBeVisible();

// ❌ Avoid - only checks DOM presence
expect(screen.getByText('Hello')).toBeInTheDocument();

No jest.clearAllMocks()

// ❌ Don't do this - it's automatic
afterEach(() => {
    jest.clearAllMocks();
});

// ✅ Mocks are automatically cleared

License

MIT