It seems like bundling jQuery into the browserify is the bottleneck right now. Either investigate browserify caching (preferable), or just bypass it for jQuery somehow specifically.
1e7a0442e0f1331e25978862d07a3571fc6a40b6 should fix this if substack/node-deputy#2 gets pulled, and published, and then browserify uses the new version.
Not C++, guys. C'mon.
It seems like bundling jQuery into the browserify is the bottleneck right now. Either investigate browserify caching (preferable), or just bypass it for jQuery somehow specifically.