module.require isn't present

In node.js, module.require is the basis for the require function. Browserify instead directly hands the require function over, without exposing any functionality as module.require.

I’m trying to browserify a module that uses defaultable, which heavily depends on the behavior of node.

It would be awesome if module.require could be at least a reference to the require function.

[jhs]

@substack, would it be possible for this to be optional or even un-documented?

We might argue about what constitutes “hacky overriding.” What I know is that we are using @fb55’s code in production and it works well. I agree with your point about spending bytes in every bundle; but I also agree with Felix’s point that supporting a documented (stability = 5, locked) feature would be nice.

We will be okay either way, just asking you to reconsider. Thanks.

[ghost]

I’m not convinced that this feature is worth supporting since it would only enable hacky overriding that probably shouldn’t be done in the first place at the expense of extra bytes in every browserify bundle.