Add support for filename [name] tags in module names.

[simonkorz]

If a file is called file.js one could use 'exports-loader?[name]' to add 'module.exports = file;' to the file.

Example usage in config:

# webpack.conf.js
module: {
    rules: [
        {
            test: /\.js$/,
            use: [
                "imports-loader?THREE=three",
                "exports-loader?THREE.[name]"
            ],
            include: helpers.root("") + "/node_modules/three/examples/js"
        }
}

This allows to use all three examples as es6 or typescript modules.

import * as THREE from "three";
import "three/examples/js/loaders/ColladaLoader";
import "three/examples/js/controls/OrbitControls";

let loader = new THREE.ColladaLoader;
let orbit = new THREE.OrbitControls;

[jsf-clabot]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

[michael-ciniawsky]

@phimonk can you please close and reopen the PR to trigger the CLA Bot again, should be working now :)

[bebraw]

It would be better with tests, but that would be a bigger change (the project doesn't have a test setup).

We could wait till test setup is in place and look into merging after that.

[joshwiens]

Given the simplicity of this particular loader, i'm going to put webpack-defaults in place now. That will solve the testing infrastructure issue.

[joshwiens]

This is also going to require an addition to the readme for the additional functionality / usecase

[michael-ciniawsky]

Closing in favor of #21 due to better documentation