volo dependencies install/update

[sam foster]

Am I right that there is currently no equivalent to an `npm install` for volo, in which an existing ./package.json is analyzed and all indicated dependencies are fetched. 

Similarly, it would be nice to do volo update or something similar, to force re-downloading of dependencies when you want to make sure you're working with the latest versions. 

Perhaps I'm missing something and this is doable today. For me, editing the package.json and saying "go do that" is a powerful way to manage dependencies in a project

Thanks, 

/Sam

[James Burke]

Doing this in the directory with the package.json that has
volo.dependencies should do what you want:

volo add

I tried to call this out in the add docs, but just pushed a small
formatting change to hopefully call it out more:

https://github.com/volojs/volo/blob/master/commands/add/doc.md

If you want to force downloading of the items in the volo.dependencies
section, pass -f:

volo add -f

James

[sam foster]

Ah ok yes I didn't notice that volo add params were optional.
But the -amd and other flags are not preserved in the package.json, so I'm not sure how to replay those? Some packages are -amd, others not.

[James Burke]

If you want -amd run on the dependencies, create an amd: {} section in
the package.json:

https://github.com/volojs/volo/wiki/Library-best-practices#wiki-packagejson

James

[sam foster]

inline:

On Friday, August 17, 2012 2:05:21 AM UTC+1, James Burke wrote:

If you want -amd run on the dependencies, create an amd: {} section in
the package.json:

https://github.com/volojs/volo/wiki/Library-best-practices#wiki-packagejson

OK got it, I didn't realize that would be smart and only attempt to convert non-AMD libraries. Will give it a whirl.

I did try `volo add` in the same directory as my package.json, and got:

"Error: Please specify an archive name or an URL"

volo add ./ took the files it found in ./*.js and added them to my baseUrl (which is ./vendor).

It maybe something fixed in the latest volo? I tried `volo rejuvenate` as I'm using  v0.1.6:

"Downloading: https://nodeload.github.com/volojs/volo/zipball/v0.2.2
Error: ENOTDIR, not a directory 'volo/.gitignore'"

..probably I'll wipe and start over.

Thanks,
/Sam

[James Burke]

Oh yeah, I switched over to npm installs as of volo 0.2.0, latest is 0.2.2. Details here:

http://tagneto.blogspot.com/2012/06/volo-020-released.html

James