Throws when using browserify and not reactify

[asgerhallas]

Seems like:

"browserify": {
    "transform": [
      [
        "reactify",
        {
          "es6": true
        }
      ]
    ]
  }

in material.ui's package.json makes browserify fail, if reactify is not installed in the application that uses material-ui.

The error is:

Error: Cannot find module 'reactify' from 'c:\workspace\client\node_modules\material-ui'

Work around is obviously to just install reactify regardless, but thought you might want to know :)

[troutowicz]

material-ui contains several .jsx files that need compiling to .js, reactify handles that transformation.

[asgerhallas]

Yes, it can do that, but I do my transformations beforehand and run browserify on pure .js files after. It's just that this config-entry is a little intrusive as to how I choose to build :)

Couldn't the config be a something the hosting application specifies?
Or if Reactify really ought to be installed in the application hosting material-ui (even if it's not used), shouldn't it be listed as a peer dependency?

[hai-cea]

This will be resolved once #179 is done.