Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

duojs.org

Post reply on HN
Print view View original

1–10 of 103 posts

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

#4

Post by bpatrianakos »

I think I'm missing something. I see how this would be great when it's build time but during development I don't want to have to keep running build commands each time I want to use a new package I'm development. Using Grunt and Bower may be a little time consuming up front but once things are set up its very easy to keep a separate Dev and prod environment in sync between different contributors. I only see the value at build time with Duo which is why I'm sure I missed something.

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

#5

Post by vkal »

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.

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

#7

Post by michaelmior »

bpatrianakos wrote: post #4

I think I'm missing something. I see how this would be great when it's build time but during development I don't want to have to keep running build commands each time I want to use a new package I'm development. Using Grunt and Bower may be a little time consuming up front but once things are set up its very easy to keep a separate Dev and prod environment in sync between different contributors. I only see the value…

Don't you already have to run some command to install the new package anyway? Not really sure I see how this is different in that respect.

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

#8

Post by TheHydroImpulse »

bpatrianakos wrote: post #4

I think I'm missing something. I see how this would be great when it's build time but during development I don't want to have to keep running build commands each time I want to use a new package I'm development. Using Grunt and Bower may be a little time consuming up front but once things are set up its very easy to keep a separate Dev and prod environment in sync between different contributors. I only see the value…

You inherently need a build step when working with remote dependencies or even any dependency. Especially when you're working with various assets like templates, css, images, etc...

Typically, let's say for an app, you'll run a watcher which will trigger the builder, so you can just spin it up and leave it alone. For smaller components that are meant for consumption, a simple Makefile is more than enough and running the command isn't too terribly bad.

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

#10

Post by tjsix »

bpatrianakos wrote: post #4

I think I'm missing something. I see how this would be great when it's build time but during development I don't want to have to keep running build commands each time I want to use a new package I'm development. Using Grunt and Bower may be a little time consuming up front but once things are set up its very easy to keep a separate Dev and prod environment in sync between different contributors. I only see the value…

It looks like the cli utility has a built in watch flag that can be passed to automatically rebuild on changes
Post reply on HN