Re:Show HN: Duo – a next-generation package manager for the ...
by anthonyshort on Thursday August 21, 2014 @03:29PM
(#8209126)
You'd use a component.json to lock it down for an app. The inline versioning is really just a way to quickly write code and get something up and running. Manifests are just a pain when you're just getting started with a project or a small script.
If a component.json is present, it'll use that to get the versions and you just require('emberjs/ember-component')
Re:Show HN: Duo – a next-generation package manager for the ...
by wycats on Thursday August 21, 2014 @03:31PM
(#8209134)
Ah. I would probably clarify the language to make it clear that having a manifest approach is the intended approach for real-world apps, but that it can be left out when playing around.
Re:Show HN: Duo – a next-generation package manager for the ...
by matthewmueller on Thursday August 21, 2014 @03:31PM
(#8209132)
The manifest is optional, so for big projects I would probably recommend using a manifest to keep all your versioning in one place.
Duo falls back to the manifest if it cannot resolve the path on it's own.
For proof of concepts and hacks though, adding a manifest is a waste of everyone's time.
Re:Show HN: Duo – a next-generation package manager for the ...
by wycats on Thursday August 21, 2014 @03:33PM
(#8209144)
I personally haven't had much trouble with:
npm install foo --save-dev
When you go beyond a single developer playing around, having a quick, well-known place to look to learn what dependencies are being used is very useful.
Re:Show HN: Duo – a next-generation package manager for the ...
by TheHydroImpulse on Thursday August 21, 2014 @03:46PM
(#8209194)
People mentioned the manifest file, but I went one step further to try and get duo to adopt a lock file: https://github.com/duojs/duo/issues/220
Am I missing something?