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

mockpack

v0.1.0

Published

Mocking of modules for unit testing with webpack 1.x

Downloads

4

Readme

mockpack

Mock out ES6/CommonJS/AMD modules imported with webpack 1.x and babel.

Basically, replaces the exports objects of a when it is imported into the module you want to test.

Example

// module.js
import { value } from './dep'

export function go() {
	return value * 100;
}

// test.js
import mockpack from 'mockpack';
const mocked = mockpack(
	require.context('.'),	// Provide a context for path resolving
	'./module',		// The module we want to test
	{			// The modules to swap out what gets exported with a fixed object
		'./dep': {
			value: 50
		}
	}
);

assert(mocked.go() === 50 * 100);

Important!

I cannot stress that this does NOT replace the entire module structure! It simply swaps out the cache for the given deps to export the object you provide and ONLY the object you provide! It does not provide partial mocking.

Running the test

npm test
// navigate to //localhost:8080/test.bundle

Why

I had an old webpack loader called proxy-loader which mocked modules by wrapping them in a factory method letting you swap out specific require statements with a different exports.

This worked well for CommonJS and AMD modules, but with ES6 imports, it got... complicated.

So I made another solution, specifically for webpack 1.x.

How

Webpack's require exposes a cache to resolve modules. I'm screwing with that cache to inject your mocked exports.