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

sisyphos

v1.1.1

Published

A utility to stub System.js dependencies

Downloads

12

Readme

sisyphos

Build Status

A utility to stub modules imported with the System.js module loader.

Installation

npm install --save-dev sisyphos

Usage

Requiring a module with stubbed dependencies happens in three phases:

  1. Declare what dependencies will be stubbed with what
  2. Import and use the module using the stubs
  3. Reset the stubs when you're done

1. Stubbing dependencies

In the example below, depA and depB have a single export. This is the case for all AMD and CommonJS modules, and for ES2015 modules which use export default. Dependencies with multiple named exports are stubbed by providing a value for each export.

sisyphos.stub({
    'path/to/depA': 'some value',
    'path/to/depB': {
        someProperty: 'someValue'
    },
    'path/to/depWithMultipleNamedExports': {
        exportA: 'valueA',
        exportB: 'valueB'
    }
});

2. Importing the module with stubs

sisyphos.require('module/that/uses/deps').then(function(mod) {
    // mod uses the stubbed dependencies
});

3. Resetting the stubs

Once you are done you can reset the dependencies to their original implementations (whether they were in the registry at the time they were stubbed or not).

sisyphos.reset(); //returns a promise

Writing unit tests

Sisyphos's promise-based API makes for easy setup and tear-down in unit tests. If you're using Mocha:

beforeEach(function() {
    sisyphos.stub({
        'some/dep': 'some_default_exported_string'
    });
    return sisyphos.require('path/to/module');
});

afterEach(function() {
    return sisyphos.reset();
});

If your test framework does not support returning promises in tests, you can attach a done callback to the promises returned by require / reset:

beforeEach(function(done) {
    // [declare stubs here]
    return sisyphos.require('path/to/module').then(done);
});

afterEach(function(done) {
    return sisyphos.reset().then(done);
});

Have a look at the tests file to see how sisyphos can be used with Mocha.

Contributing

If you want to run the sisyphos tests suite, clone it locally and run:

npm install
npm test

License

MIT

Acknowledgements

Special thanks to @mroderick for creating bogus, a utility to stub dependencies in Require.js projects.