briancavalier/rave-wire — pull request #2 by unscriptable (2014-07-28 23:33:07+00:00)
Title: Add explicit peer dependencies for wire and a domReady implementation

This looks like a no-brainer kind of PR, but I'm submitting it to ensure that we agree on this approach. Specifically, we're adding wire and rave-curl-domReady as explicit peer dependencies.

Imho, there is no controversy whether *wire* should be a peer dependency. When we first created this repo, we weren't sure if peer dependencies were the correct concept. Now, I think we are sure.

The more interesting part is the [peer] dependency on rave-curl-domReady. At the moment, the rave-amd-plugins extension (which rave-curl-domReady uses) does not allow simultaneous, duplicate plugins to coexist. Plugins are applied globally (to the whole project, including third-party packages). If the user also installs another domReady plugin extension such as rave-requirejs-domReady*, then the rave-amd-plugins extension will *randomly* use either of the domReady plugins.

This is likely a moot problem since most (if not all) domReady AMD plugins work the same and rave-curl-domReady is the only AMD plugin extension for rave *at the moment*.

\* doesn't actually exist. just for example