The title is a bit misleading. Only a small part of the article mentions Browserify. I was hoping for the authors take on the struggles and efficiencies, as I'm at the point where I need to make the decision to use Browserify for my companies client heavy apps.
I'm using browserify to share code between the client and server, and it works just how you want it to. The api is very simple. There's a command line utility, but I decided to use the direct API to integrate it with my build system. You give it the files you want to bundle up, and then it gives you an output stream. Super simple, and works with no hassles.
The only problem I had was with recursive requires, but I created a pull request fixing the problem, and the team was very responsive about getting it fixed. The fix was integrated and put out the same day, so I didn't have to deal with any delays.
Er ... "I can now grab the user's webcam stream, generate a GIF, and let the user download or share it on an image hosting platform. And all of this is done in the front-end using a lightweight interface!" ... that's 3 lines (sorry: 4) of native JS, we need node-modules for this?
This blew my mind. I've been dabbling in Node, but I had no idea this much was possible. The GifMe demo would have been nearly enough, but wow, thanks for posting this.
hellopat|12 years ago
etler|12 years ago
The only problem I had was with recursive requires, but I created a pull request fixing the problem, and the team was very responsive about getting it fixed. The fix was integrated and put out the same day, so I didn't have to deal with any delays.
fraserxv|12 years ago
taterbase|12 years ago
masswerk|12 years ago
secoif|12 years ago
smrtinsert|12 years ago
joemaller1|12 years ago