We just started playing with idea recently and found that browserify has some trouble with relative require paths that hem handles as expected.
I think we just need to setup some transformations in browserify to make it work more like hem.
For example, with hem I can require('./foo') and that will include foo.js relative to my current directory, whereas browserify translates ./foo as from the app/ directory (in the case of a spine app). I like using the relative paths that hem allows because it makes it super easy to move directories around if I need/want to reorganize the project.
hem also allows me to do require('bar') where 'bar' is not a node module, but just a top level bar.js file. hem also allows me to do require('bar/baz') to require a bar/baz.js relative to the app/ directory whereas browserify wants me to do require('./bar/baz').
Suggestions welcome.
Thanks!