My goal here is to have all functionality coming from one js file (for easy portability to other platforms). I have mostly accomplished this with Browserify, but it could still be better. Browserify is a bit brittle and I don't like what it does to scope. Right now it is compiling and wrapping stylus and html files, which can then be required on the frontend. I'm using some custom transforms in /my_modules to do this but they are janky.
My goal here is to have all functionality coming from one js file (for easy portability to other platforms). I have mostly accomplished this with Browserify, but it could still be better. Browserify is a bit brittle and I don't like what it does to scope. Right now it is compiling and wrapping stylus and html files, which can then be required on the frontend. I'm using some custom transforms in /my_modules to do this but they are janky.
It could be done with a 2 step process like this: http://stackoverflow.com/questions/21072880/is-there-a-way-to-rewrite-the-html-to-use-gulp-minified-css/21249167#21249167, in combination with gulp-inject. The idea is to have a build step for assets like html, css, and images (images would be turned into data-uris). The js build step then watches the destination folder, and includes the processed assets with gulp-include.
This is low priority.