Running with node instead of browserify

Would be helpful for things like `fs` to use this with node.

Maybe each node could be their own process (this would allow to use other CLI tools as well), which are piped together.

The issue names Node, browserify, fs, separate processes, and piped CLI tools, but no files or tests. Start by locating the current browserify execution path and graph runner; done should mean a clearly defined, tested way to run nodes under Node with fs access and process piping.

Written by the indexing model from the issue text.