http-browserify

> (why isn't this a separate npm module, btw?) It is[0]. It's a dependency of browserify. If you don't use it, part of the concat+minification step prunes dead code. > To make my own privately held modules and install them properly, I have to run a npm server? This seems like an awful lot of work for something as basic as this. Ok, so now I can use the cloud for this, but come on, I should be able to do this just from within the filesystem, like e.g. git does it. If you don't care about having your package published somewhere other than your local machine, you can use npm link[1], or `npm install <directory>`[2]. 0. https://github.com/substack/http-browserify/ 1. https://docs.npmjs.com/cli/link 2. https://docs.npmjs.com/cli/install

Thanks; great response. I had forgotten about crossovers. I did a little project in CLJS and found the additional power of the language nice, but not revolutionary. I've found getting into Node.js that despite the well-known warts of JavaScript, the community has done an amazing job working around those problems, building powerful abstractions, and shipping simple, un-complected code. I hardly feel like I'm compromising on expressivity. So for me, language like "callback hell" and "wasteful" rings a bit hollow, as it doesn't reflect my experience writing JavaScript. In fact, if I were a contributor to When.js I could imagine it being pretty insulting. Maybe we can win more people to ClojureScript by recognizing, not diminishing, the great stuff folks have made with vanilla JS, and showing how CLJS provides interop while making JavaScript