Yep good reminder on the docs. I'll update those before the end.

Forward integrated with master branch and resolved a couple conflicts.

I've added a test to verify CommonJS lookup works, when using an alternative fs. The test fails currently, but once the module-definition dependency has had the outstanding PR merged, and we update it to the new version in package.json then the test should pass. Test passing.

@mrjoelkemp
I'm looking at the web pack resolver now!
I noticed that the webpack config file is brought in with a require call, and then executed if its a function:

 loadedConfig = require(webpackConfig);

    if (typeof loadedConfig === 'function') {
      loadedConfig = loadedConfig();
    }

I assume the require call means that node will resolve it on disk - meaning it will bypass the opportunity of going through an alternative fs implementation. Any thoughts on this? Do you think we could load it from an fs instead somehow? Or will the webpack config file always have to live on nodejs default 'fs`?

@dazinator You can probably read it from your fs then json parse it.

Webpack enhanced resolve has now been updated to support passing a custom fs in:
webpack/enhanced-resolve#172 so can probably resume work on this now.

note to self: update to latest release of enhanced-resolve to provide custom fs implementation: https://www.npmjs.com/package/enhanced-resolve