Duo

This looks superb. Great work.

I love simple things, this gets my +1, look forward to learning more. I can't see why this is browser only, am I missing something?

Author here. @tomdale We're on the same page. I've worked with many large JS codebases as well and consistency and repeatability are a must. However, as with any tool, it's…

you can require two different versions of the same library and it works just fine. uses a similar process as browserify.

With Duo you can actually have multiple versions of the same Javascript dependency. And then you can use the CLI to figure out what duplicates you have if you want to slim them…

It sounds like this means that if I wanted to use a specific version of Ember, I would have something like the following line in many files: ```…

I'm not sure this actually improves the flow for me. I (like most sane devs), like to lock my deps to specific versions (or vendor them). Currently, it's just a matter of…

One question I always ask when looking at a package manager is, "Will this help me have reproducible builds?" (http://martinfowler.com/bliki/ReproducibleBuild.html) I've worked…

I have a hard time seeing what exactly the point of having another package manager is. We already have a very established way of managing front-end packages: NPM and Browserify.…

I like the ideas, but it feels like it's just a small incremental step over established solutions like webpack and browserify. Does this have any more to offer other than…

npm supports git repositories as dependencies already (git://github.com/...), so that feature doesn't seem like much added value to me. And considering that any real project…

> In Duo you can pin down any dependency right in the file via require('some/repo@tag'), which is the same as having a manifest with a pinned version. That will do nasty things…

Let's say your app my_app uses foo and bar. They both use baz. You give them each their own version of baz: foo gets baz 1.0 and bar gets baz 2.0. Now, at runtime: ``` my_app…

Mutation isn't necessary to demonstrate the problem. Consider three libraries: first, there's a basic, widely-used datetime library. There's also a timezone library depending on…

Is there support for symlinking for easy development? I mean the equivalent for 'npm link' or 'bower link'. Also, can you host your own "duo registry" (if the concept makes sense…

Is there support for symlinking for easy development? I mean the equivalent for 'npm link' or 'bower link'. Also, can you host your own "duo registry" (if the concept makes sense…

Maybe it's just me but having no manifest makes using this tool quite painful. It has taken me 10 mins just to figure out how to structure the require()'s so that it doesn't…

I like the ideas, but it feels like it's just a small incremental step over established solutions like webpack and browserify. Does this have any more to offer other than…

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…

Did Duo the same as gulp+browserify ?

Is it fast during development on large codebases? (e.g. by compiling incrementally)

One question I always ask when looking at a package manager is, "Will this help me have reproducible builds?" (http://martinfowler.com/bliki/ReproducibleBuild.html) I've worked…

I have a hard time seeing what exactly the point of having another package manager is. We already have a very established way of managing front-end packages: NPM and Browserify.…

npm supports git repositories as dependencies already (git://github.com/...), so that feature doesn't seem like much added value to me. And considering that any real project…

I like the ideas, but it feels like it's just a small incremental step over established solutions like webpack and browserify. Does this have any more to offer other than…

But, but.. I _just_ decided to use webpack :( More seriously: do you feel like it incorporates all the lessons of its predecessors?

People interested in Duo may also want to have a look at jspm.io. It solves a similar problem, but with a few differences which to me are advantages: - Transparently supports…

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 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…