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

@nmock/jest

v0.1.1

Published

Jest compatible module mocking for node:test runner.

Downloads

112

Readme

@nmock/jest

Jest compatible module mocking for node:test runner.

Installation

npm add -D @nmock/jest

Usage

Add --import @nmock/jest/register option to the Node.js command line.

node --test --import @nmock/jest/register './tests/**/*.test.ts'

If you are testing a TypeScript project, you can combine it with --experimental-strip-types.

node --test --experimental-strip-types --import @nmock/jest/register './tests/**/*.test.ts'

Or, you can use a 3rd-party hook to resolve modules, such as @swc-node/register.

node --test --import @swc-node/register/esm-register --import @nmock/jest/register './tests/**/*/.test.ts'

[!WARNING] Make sure you import the 3rd-party hook BEFORE @nmock/jest/register as ESM customisation hooks are chained against the imported order.

Advanced Usage

If you want to customise how to install the hook, you can use your own module with the programmatic API.

import { install } from "@nmock/jest";

install({
  globals: true, // Enable the global `jest` object
})

Writing mocks

Automatic mocking

Call mock() with only the module name to be mocked, then all exported functions will be mocked automatically.

import { mock } from "@nmock/jest";

mock("./your-module.js");

Manual mocking

Call mock() with a factory function to define how to mock the module.

import { mock } from "@nmock/jest";

mock("./your-module.js", () => ({
  doSomething: () => {
    console.log("doSomething was called!");

    return "Hello, world!";
  },
}));

Limitations

  • As mock() calls will be executed outside the module, any other symbols cannot be referenced from the mock.
    • This behaviour is similar to vi.mock.
  • Some other APIs including requireActual are not implemented yet.