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

hijackdi

v1.1.3

Published

Library for injecting fake/mocked dependencies in tests

Downloads

3

Readme

HijackDI

Build Status

HijackDI provides a way of mocking, faking or stubbing external dependencies that are loaded via require() in nodejs.

HijackDI provides a sandbox environment for you to run your tests within. In this environment node modules or classes which are required are switched with your fakes or mocks. This works at any level, not just at the subject meaning HikackDI is perfect for integration or unit testing.

See the examples folder for more.

##Installation

The easiest way to install is through the Node Package Manager (NPM)

    npm install hijackdi

##Usage

If we have the following class...

MyClass.js

    var bob = require('bob'),
        jimmy = require('./jimmy.js');
        
    var MyClass = function(){
        this.do = function(){
            return bob() + ' ' +jimmy();
        }
    };
    
    module.exports = MyClass;

...we could mock, stub or fake out the require(s) using HijackDI. The test below demonstrates how this is done.

Test.js

    require('chai').should();
    var Hijackdi = require('hijackdi');
    
    var hijackdi = new Hijackdi('MyClass.js'),
    stubs = {
        'bob' : function(){ return 'hello'; },
        './jimmy.js' : function(){ return 'world'; }
    };
            
    test('a test', function(){
    
    	hijackdi.sandbox(stubs,function(MyClass){
    	    var myClass = new MyClass();
    	    myClass.do().should.equal('hello world');
    	});
    	
    });

The hijack object created has a sandbox method that takes an object literal containing the external dependencies that you wish to replace. The function supplied in this method is the code executed whilst the dependencies are replaced. After execution of this function the mocked/stubbed/faked dependencies are removed.

##API

    var HijackDi = require('hijackdi');
    
    /*
        This constructs a hijackdi object with a subject. The subject will have
        the dependencies you specify switched for your mocks. Any other
        dependencies will remain intact. 
    */
    var hijackdi = new HijackDi('../lib/MySubjectClass.js');
    
    /*
        definition of the fake dependencies. These will replace the real object
        in the sanbox environment. To fake out your own objects the key should be the 
        relative path from the test file. For a node_module just use the module name.
    */
    
    fakes = {
        '../lib/someDependency.js': function(){ return 'hello';},
        'redis' : { createClient: function(){ return fakeRedisClient; }}
    };
    
    /*
        Within the sanbox mode redis and ../lib/someDependency.js are switche out.
        Any other subdependency will be intact. If another subdependen ALSO required redis,
        it will get our fake too.
    */
    
    hijackdi.sandbox(fakes,function(MySubjectClass){
        var mySubjectClass = MySubjectClass(); //with our fake subdependencies 
        var redis = require('redis'); // fake redis (why are you requiring here??)
    });