Separate lib/pre-binding.js into its own npm module?

Nobody has claimed this yet.

This is just a thought, so please bear with me here...

node-pre-gyp's dependencies have rather large file sizes (i.e. request weighs 2.6MB), and node-pre-gyp weights over 4MB! For this reason, I'd like to bundle my pre-compiled module into a nice, small tarball that doesn't need node-pre-gyp as a dependency; however, I like that node-pre-gyp replaces the npm bindings module with the following code:

``` javascript
var binary = require('node-pre-gyp');
var path = require('path');
var binding_path = binary.find(path.resolve(path.join(__dirname,'./package.json')));
var binding = require(binding_path);
```

Is there any way that the functionality of `lib/pre-binding.js` could be separated into another npm module that is required by node-pre-gyp? That way, I could easily delete node-pre-gyp as a dependency after building/installation and still have the binding path determined dynamically.

Does that make sense? Thoughts on this?

Start by reviewing lib/pre-binding.js and the package.json-based binding lookup shown in the issue, then trace how node-pre-gyp exposes that functionality. Determine whether extracting it into a separate npm module is viable and define the module boundary, dependency behavior, and compatibility expectations. Done means the proposal has a decided scope and an implementation path.

Written by the indexing model from the issue text.