Improve support for CommonJS usage

[linclark]

As folks brought up in angular/material#1655, people using tools like Browserify will expect that angular-animate and angular-aria will be required in index.js. Since they are listed as dependencies, they will have already been downloaded and will be available to the module system.

You don't actually need to use the path, so the possible path variations won't be a problem. When Browserify is processing the file, it uses Node's module resolution to figure out that require('angular-animate') should use path/to/angular-animate. This is one of the advantages of Browserify and CommonJS support. It means that apps which use angular-material don't need to hardcode paths for angular-material's dependencies.

[linclark]

I created a demo to show this working. It's currently using my fork (which has this change in it) as the npm dependency.

[jgoux]

👍 for this as well !
I won't need browserify-shim anymore :

"browser": {
    "angular-animate": "./node_modules/angular-animate/angular-animate.js",
    "angular-aria": "./node_modules/angular-aria/angular-aria.js",
    "angular-material": "./node_modules/angular-material/angular-material.js",
  },
  "browserify": {
    "transform": [
      "browserify-shim"
    ]
  },
  "browserify-shim": {
    "angular-material": {
      "depends": [
        "angular-animate",
        "angular-aria"
      ]
    },

[ThomasBurleson]

@linclark - would we not also want to do the same Angular?

// Load Angular and dependent libs
require('angular');
require('angular-animate');
require('angular-aria');

// Now load Angular Material
 require('./angular-material');

// Export namespace
 module.exports = 'ngMaterial';