specifying browserify options (plugins, extensions)

ref #285, #262

currently you can only specify browserify transforms using the browserify.transform key in package.json. altlangs like typescript and coffeescript use custom (non-.js) extensions though which cannot be configured in package.json.

@yoshuawuyts & i chatted about this recently–adding some custom logic to bankai that reads additional configuration from the application’s package.json only (not from package.json in dependencies) could be a nice option:

// for typescript
{
  "browserify": {
    "plugin": [ "tsify" ]
  }
}
// for coffeescript
{
  "browserify": {
    "extensions": [ ".coffee" ],
    "transform": [ "coffeeify" ]
  }
}

this still leaves out plugins that need things like functions in their options, but you could work around that by wrapping it in a small plugin like so:

// package.json
{
  "browserify": {
    "plugin": [ "./browserifyConfig" ]
  }
}
// browserifyConfig.js
module.exports = function (b) {
  b.plugin('some-plugin', { option: function () {} })
}

anyone have more thoughts on this?

[s3ththompson]

Just ran into this issue as well! Custom logic seems a bit hacky–is there any chance @substack would accept an upstream PR to add something like this to browserify core?

Alternately, perhaps we could carve out a typescript-specific solution? I feel like now that Choo has typescript support it would be great if Bankai supported it out-of-the-box too!

[yoshuawuyts]

@goto-bus-stop yeah, that seems reasonable!