Possible fix for #10

[silkentrance]

• fixes #10: user must now pass in calling module, uses user module to require() modules/files

Have a look. I know that this will break the existing API. It will, however, make the behavior of load() similar to require() so that load() can be used as a drop-in replacement.

This might even go so far as to register the load function as the new require function in the user module, e.g.

var rechoir = require('rechoir')(module);
require = rechoir.load;

var sumfing = require('latest-stats.csv');
...

What do you think?

[silkentrance]

And maybe we can get rid of resolve-sync altogether now that we have the module's require() function?

I do not know, however, if require and module.require are essentially the same function, as require has a few more properties assigned to it.

According to http://nodejs.org/api/modules.html#modules_module_require_id they behave exactly the same.

[silkentrance]

@tkellen merged master, all seems to be well

[tkellen]

Can you rebase to a single commit and then we'll merge this?

[silkentrance]

Uh oh, never done this before. Will try. Also need to add parameter checking.

[silkentrance]

Hope that the latest commit does the trick...

[silkentrance]

Erm, rebasing with published commits seems to be a no-no... Well, cherry pick then? Otherwise I will tear down the branch and recreate it and then we can merge the single commit in the new branch.

[tkellen]

if you rebase/squash you can force push over your old commits and this will automatically update the PR

[silkentrance]

Seems to be ok, when trying to push I get 'everything is up to date'... and I already did the merge, so... you can simply merge 19110c2 as it already contains the changes merged from master...

[silkentrance]

Okay, forced push, forgot to rebase --continue...

[silkentrance]

Thanks for pointing me towards rebase!

[silkentrance]

With load() going to be removed this is now obsolete.