The problem with doing this via npm is that npm works with the
dependencies from the package.json which is a problem for plugins,
since they are seldom known at the time the package.json is writeen.
I have done something like this for my app. What I ended up doing is
simply defining a folder which
> What I ended up doing is simply defining a folder which all plugins
have to be in.
That seems to be a good minimalist approach.
One requirement for this project is for plugin developers to be able to
easily publish their plugins so that every app user can select which
plugins to use. So some
