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

load-mocks

v1.0.1

Published

Monkey patch the _load function from require to load a mock, if present.

Downloads

4

Readme

load-mocks Build Status npm

This module basically extends the __mocks__ folder functionality of jest, but outside of the jest runtime. Likely you'll want to conditionally load this on a test server based on an environmental variable.

What this does

By modifying the _load function, any module which requires some other module will first check if there is a mock present for that module. If so, we'll load that mock. If not, we'll load the actual module.

The mock must be placed in a __mocks__ folder in the same folder as the module which needs to load the mock. A module in any other folder will not load the mock, including nested folders. Because of this feature, you can require the original module from the mock of a module. E.g. in __mocks__/fs.js you can still require('fs') and get the original fs built-in module. This is helpful if you only want to mock a portion of a module.

Why would you want to do this?

This isn't intended for use in production apps, but is rather a way to mock certain conditions that can be tested. An application deployed to a test environment, may conditionally load this package so that certain api responses or error conditions may be mocked.

For example, if you depend on an external API you could mock the data fetch and return an error, or some fixture data, from that API instead. This allows you to easily perform an end-to-end test on a test server.