3 ms·
Browserify is wonderful. I had trouble with browserify-middleware on nodejs, because it took so long to load -- several seconds, compared with under 1 second u
by jnbiche 13y ago
Browserify is wonderful. I had trouble with browserify-middleware on nodejs, because it took so long to load -- several seconds, compared with under 1 second using the browserify "binary" tool. So I paired the browserify binary with livereload and grunt-contrib-watch, and it's now a very quick process every time I change the code.
However, it doesn't at all address the issue of losing JavaScript state upon reload, which is one of the main problems this post is emphasizing.
- davemo 13y agoBetween browserify and requirejs I've definitely had a more positive experience with the former but my experience is that both seem to be subject to scaling problems with even a trivial number of dependencies in play; I wish there was a really good sample project setup that would allow accurate comparisons between the tools at the scale they are frequently used at, but for now I choose to use simple concatenation and a simple namespacing tool [1] to avoid lengthy watch-time issues during development. grunt-contrib-watch is a pretty vital part of my workflow, but I don't use the livereload options because I can't afford to lose that state in the browser. [1] - https://github.com/searls/extend.js https://github.com/searls/extend.js
- tlrobinson 13y ago"the issue of losing JavaScript state upon reload" Is this really that desirable? I can imagine a lot of scenarios where this would cause unexpected behavior. Most other platforms don't support this, do they?