"Offline" interface precompilation

Nobody has claimed this yet.

Here's another thought, related to #18. For a library like [multiplex](https://github.com/maxogden/multiplex) and probably many other cases, why not let them eliminate the "schema compilation" step at that level entirely?

What I mean is this use case:

Say someone wants to use 'multiplex', they simply `npm install multiplex` and use its API. (They maybe don't even care that it uses protocol buffers "under the hood", they're just happy that things seem to be fast/efficient.) Why should they end up needing to install 'generate-function' and similar packages, and re-parsing the schema files every time their script starts?

Ideally, a library like 'multiplex' could instead use `devDependencies` and a `prepublish` script to pre-compile the schemas, and then all the published package itself would require, just a file containing the pre-generated code! (The Handlebars template engine offers [a pre-compilation option](https://github.com/wycats/handlebars.js/blob/62ed555b2c8d9e0fd37a1384dadfaeb3a7a94e61/README.markdown#precompiling-templates) kinda like this, for example.)

No source files or tests are named. Start by reviewing related issue #18 and the package's npm publishing flow, including the proposed devDependencies and prepublish approach. Done means consumers can install the published package and use generated schema code without installing generation tools or recompiling schemas at startup.

Written by the indexing model from the issue text.