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

jest-get-mocks

v0.0.1

Published

Recursively find mocks in your source code for your projects Jest config

Downloads

4

Readme

jest-get-mocks

Recursively find mocks in your source code for your projects Jest config. Returns a flattened object of absolute (global mocks) and relative path key:value (<module_name>:<mock_function_path> pairs by searching a directory for mock functions. For global mocks, found folders will be recursively searched and treated as scoped modules. For relative mocks, found folders will be recursively searched for __mocks__ folders.

Note: For relative mocks, excludes <rootDir>/src/__mocks__, but includes <rootDir>/src/ ** /__mocks__/ *.

Install

Using NPM

$ npm install --save-dev jest-get-mocks

Using Yarn

$ yarn add --dev jest-get-mocks

Usage

Import the package then apply the results to your moduleNameMapper field in your jest configuration.

const jestGetMocks = require('jest-get-mocks');
const path = require('path');

const mocks = jestGetMocks({
  /** The directory for your global/module mocks (optional). */
  globalMocksDir: path.resolve(__dirname, 'src/__mocks__'),
  /** The project root directory. Typically where your jest.config.js is. */
  rootDir: path.resolve(__dirname),
  /** The projects source directory. */
  srcDir: path.resolve(__dirname, 'src'),
    /**
   * File names to exclude, can be partial names.
   * Defaults to `['spec.js', 'spec.jsx', 'spec.ts', 'spec.tsx', 'snap', 'jest.setup.js', 'jest.setup.ts']`.
   */
  excludeFiles: ['spec.js', 'spec.jsx', 'spec.ts', 'spec.tsx', 'snap', 'jest.setup.js', 'jest.setup.ts'];
  /**
   * An array of file extensions your modules use.
   * Defaults to `['js', 'jsx', 'ts', 'tsx']`;
   */
  moduleFileExtensions: ['js', 'jsx', 'ts', 'tsx'];
});

module.exports = {
  moduleNameMapper: {
    ...mocks,
  },
};

If you run the example in the ./demo folder your moduleNameMapper will look like the following:

module.exports = {
  moduleNameMapper: {
    fs: '<rootDir>/src/__mocks__/fs',
    uuid: '<rootDir>/src/__mocks__/uuid',
    '\\/now$': '<rootDir>/src/utils/__mocks__/now',
  },
};

Contributing

Run, yarn lint && yarn test