Configure plugins via package.json similar to `browserify.transform`

Configuring transforms via the browserify.transform field in package.json is lovely. It’s a great way to configure browserify once regardless where/how browserify is executed (manually or via npm script or other).

It would be even more lovely to support configuring plugins via package.json as well.

[jasonkarns]

So this is an issue if dependencies specify a browserify plugin in their package.json. Since plugins can only be specified at the command line (or via the API), there is currently no way to have a plugin only apply to a dependency.

So could this feature be implemented by having browserify only respect the browserify.plugin field at the top level? That way specifying a package.json thusly:

"browserify": {
  "plugin": [ "my-plugin" ]
}

is identical to browserify -p my-plugin. Any browserify.plugin fields in dependencies are ignored.

(If I understand the issue correctly)

[ahmadrasyidsalim]

+1