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 🙏

© 2025 – Pkg Stats / Ryan Hefner

require-proxy-mock

v0.6.1

Published

Mock require calls using ES6 Proxy

Downloads

10

Readme

require-proxy-mock

Automatically and transparently patches all require calls (Module._load) to return an ES6 Proxy wrapper around the original module's export(s) which can later be mocked/unmocked as required.

Somewhat similar to proxyquire, rewire, and Jest's automock.

Requires Node v6+ (try 10+ if you're getting errors like this)

Install

npm install --save-dev require-proxy-mock

Usage

API

const { mock } = require('require-proxy-mock')
mock(dep, mock)
mock({dep: mock, ...})
mock(Map {dep => mock, ...})
  • dep [string|regex] Require request of the dependency to mock.

  • mock Mock that replaces the required dependency.

Example

Important: Require once before loading any other modules:

mocha --require require-proxy-mock **/*.test.js

Then require it as an object in your test(s) and add/remove properties on it with the same key names as the originally required files you want to mock:

  • main.js - A typical module file; no change required here

    const someLib = require('some-lib')
                             ^^^^^^^^ will be mocked
    module.exports = someLib
    • some-lib.js - Dependency that'll be mocked

      module.exports = () => 'ORIGINAL'
  • main.test.js

    const {mock} = require('require-proxy-mock')
    const main = require('./main')
    
    describe('main', () => {
      let unmock
      before(() => {
        unmock = mock('some-lib', () => 'CHANGED')
                       ^^^^^^^^ mocked
      })
      it('should mock', () => {
        assert(main(), 'CHANGED')
      })
      after(() => {
        unmock()
      })
    })

Limitations

Cannot mock primitives (since they can't be proxied).