Show HN: Duo – a next-generation package manager for the front end

Re:Show HN: Duo – a next-generation package manager for the ... by vkal on Thursday August 21, 2014 @02:15PM (#8208763)

So earlier this summer I learned how to use RequireJS + a smidgen of Grunt, then I felt the need to move towards Gulp and Browserify (which I've just recently started), and now I'm excited about Duo.

It would be interesting for someone with more expertise to do a compare/contrast further down the line of all three.

"...I show you how deep the rabbit hole goes" - Morpheus

Also, does someone know how the Closure compiler fits into all of this? It might be totally unrelated but I'm trying to learn more about JavaScript application architecture, and I'm not sure where that fits in.

[ Parent | on HN ]

Re:Show HN: Duo – a next-generation package manager for the ... by cel1ne on Friday August 22, 2014 @07:17AM (#8211618)

I tried a lot and use RequireJS + Gulp now (same Gulpfile on every project). Works for me, I don't see a compelling reason to change something.

My Gulpfile has 200 lines and does everything from asset-manifests to css minification, js-reloading etc.

[ Parent | on HN ]

Re:Show HN: Duo – a next-generation package manager for the ... by munificent on Thursday August 21, 2014 @05:47PM (#8209821)

> I felt the need to move towards Gulp and Browserify

Dude, you're so behind the times. It's Yeoman and Bower now. Wait, Broccoli and Duo.

[ Parent | on HN ]

Re:Show HN: Duo – a next-generation package manager for the ... by Gigablah on Thursday August 21, 2014 @08:33PM (#8210393)

Yeoman isn't a build tool though, it just generates the application skeleton.

[ Parent | on HN ]