Proxyquire cannot stub non-object imports about proxyquire HOT 9 CLOSED

I think it would be great if the README had at least one example for stubbing a module that exports a single function directly. It's such a common use-case.

from proxyquire.

I was able to get a "primitive" mocked by doing:

var mocked = proxyquire('./path/to/thing', {
  'path/to/primitive': (function() {
    var s = new String('foo');
    s['@global'] = true; // probably not necessary for your example, but I needed this
    return s;
  }()),
});

If you don't need the global mock, you could probably just use:

var mocked = proxyquire('./path/to/thing', {
  'path/to/primitive': new String('foo')
});

It's not 100% the same, but for me it was close enough.

from proxyquire.

@kirbysayshi fair enough, but worth noting that this way won't work for any module that exports a number or a boolean value

from proxyquire.

@ninjatronic the above suggestion solves your problem right?
Do you really have cases where you export a number? I'm not sure if there are enough cases to make it worth supporting in proxyquire.

@kirbysayshi could you please add your solution to this wiki page? I'll link it from the readme once you do.

Thanks.

from proxyquire.

@thlorenz done! Any feedback is very appreciated

from proxyquire.

Thanks @kirbysayshi. Looks good.
Once @ninjatronic's PR makes it in, we may not need any caveats anymore as primitives will just work then.

from proxyquire.

PR landed

from proxyquire.

@thlorenz thanks :)

from proxyquire.

@raine PRs welcome :)

from proxyquire.