"Volo add" zip searches in wrong path

70 views
Skip to first unread message

Rafael B

unread,
Apr 29, 2013, 6:20:05 PM4/29/13
to vol...@googlegroups.com
I'm trying to add the jquery-ui-map plugin, but for some reason volo is prepending the path with "download/", which doesn't exist in zip !

$ volo add https://jquery-ui-map.googlecode.com/files/jquery-ui-map-3.0-rc.zip#ui/jquery.ui.map.js jquery.ui.map

ERROR: Error: ENOENT, no such file or directory '/tmp/temp-jquery.ui.map-1367273514804-1/download/ui/jquery.ui.map.js'


Another example, I'm trying to add a js file from zip, which isn't in a specific folder, so I specify ./jflickrfeed.js but volo searches in colorbox/jflickrfeed.js - colorbox/ folder does exist in zip, but I specifically asked for a file in the root.

$ volo add http://files.gethifi.com/posts/jflickrfeed/jflickrfeed.zip#./jflickrfeed.js jflickrfeed

ERROR: Error: ENOENT, no such file or directory '/tmp/temp-jflickrfeed-1367273753857-1/colorbox/jflickrfeed.js'

Thanks!

James Burke

unread,
May 7, 2013, 4:30:17 PM5/7/13
to vol...@googlegroups.com
What version of volo are you using (just type `volo` to get version)?
I fixed something like this in a more recent release, the latest
release is 0.2.10.

James
> --
> You received this message because you are subscribed to the Google Groups
> "volojs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to volojs+un...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Rafael B

unread,
May 7, 2013, 6:57:36 PM5/7/13
to vol...@googlegroups.com
I'm trying to update from v0.2.9 to v0.2.10 but I'm getting this error:
npm WARN package.json vo...@0.2.10 No repository field

Looks like volojs is missing a required 'repository' field in package.json...  Weird.

James Burke

unread,
May 7, 2013, 7:07:44 PM5/7/13
to vol...@googlegroups.com
That looks like just a warning, so it should have installed fine, just
npm being cranky. I will look at adding it though to avoid the issue
in the future.

For reference, what version of nodejs are you using, so I can reproduce?

James

Rafael B

unread,
May 7, 2013, 7:13:15 PM5/7/13
to vol...@googlegroups.com
I'm still left with volo v0.2.9 though !

nodejs v0.10.5
npm v1.2.19

This is the full output:

$ sudo npm -g update volo
npm WARN package.json vo...@0.2.10 No repository field.
npm WARN package.json datef...@1.0.2-1.2.3 No repository field.
npm WARN package.json evente...@0.4.11 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json alm...@0.2.5 No repository field.
npm WARN package.json requ...@2.1.4 No repository field.
npm WARN package.json bo...@0.3.2 No repository field.
npm WARN package.json faye-we...@0.4.4 No repository field.
npm WARN package.json faye-we...@0.4.4 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json requ...@2.0.6 No repository field.
npm WARN package.json jsh...@0.7.3 No repository field.
npm WARN package.json vo...@0.6.4 No repository field.
npm WARN package.json formi...@1.0.9 No repository field.
npm WARN package.json cheerio...@0.0.3 No repository field.
npm WARN package.json gr...@1.7.0 No repository field.
npm WARN package.json ey...@0.1.8 No repository field.
npm WARN package.json ct...@0.5.2 No repository field.
npm WARN package.json asser...@0.1.2 No repository field.
npm WARN package.json github-ur...@1.1.1 No repository field.

James Burke

unread,
May 7, 2013, 7:17:52 PM5/7/13
to vol...@googlegroups.com
I just did a force update adding the repository field. I am surprised
it led to a failure to install though, it i s just a warning. If it
still fails, I have used install instead of update: npm -g install
volo. Maybe that works?

James

Rafael B

unread,
May 7, 2013, 7:22:49 PM5/7/13
to vol...@googlegroups.com
Nope. Still doesn't work:

$ sudo npm -g install volo
npm WARN package.json vo...@0.2.10 No repository field.
/usr/bin/volo -> /usr/lib/node_modules/volo/bin/volo
npm WARN package.json datef...@1.0.2-1.2.3 No repository field.
npm WARN package.json evente...@0.4.11 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json alm...@0.2.5 No repository field.
npm WARN package.json requ...@2.1.4 No repository field.
npm WARN package.json bo...@0.3.2 No repository field.
npm WARN package.json faye-we...@0.4.4 No repository field.
npm WARN package.json faye-we...@0.4.4 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json requ...@2.0.6 No repository field.
npm WARN package.json vo...@0.6.4 No repository field.
npm WARN package.json cheerio...@0.0.3 No repository field.
npm WARN package.json formi...@1.0.9 No repository field.
npm WARN package.json jsh...@0.7.3 No repository field.
npm WARN package.json gr...@1.7.0 No repository field.
npm WARN package.json ey...@0.1.8 No repository field.
npm WARN package.json github-ur...@1.1.1 No repository field.
npm WARN package.json asser...@0.1.2 No repository field.
npm WARN package.json ct...@0.5.2 No repository field.
vo...@0.2.10 /usr/lib/node_modules/volo
├── wh...@1.0.5
├── shell...@0.0.1
├── sem...@1.0.14
├── q...@0.8.5
├── ugli...@1.2.6
└── z...@0.0.6 (q-io-...@0.0.2, q-...@0.0.11, q...@0.7.2)

$ volo -v
volo v0.2.9, a JavaScript tool to make JavaScript projects. Allowed commands:

James Burke

unread,
May 7, 2013, 7:29:45 PM5/7/13
to vol...@googlegroups.com
There may be a cache issue, so waiting a bit may help? Also, it may be
`npm install -g volo` ?

When I try grabbing http://registry.npmjs.org/volo/-/volo-0.2.10.tgz
directly and unzipping it, it seems to have the right package.json
with repository content for me.

James

Rafael B

unread,
May 7, 2013, 7:39:09 PM5/7/13
to vol...@googlegroups.com
Same thing with: $ sudo npm install -g volo
Thing is, I've been trying to upgrade volo for the past 1-2 weeks..
Since I saw that 0.2.10 is out already.. But to no avail..

Downloaded the tgz directly, and indeed saw the package.json.. 

This is just weird.. :(

Rafael B

unread,
May 30, 2013, 9:45:08 AM5/30/13
to vol...@googlegroups.com
Finally, SOLVED:

$ sudo npm -g uninstall volo
$ rm -rf ~/.npm/volo
$ sudo npm -g install volo

I guess `npm` had some issues with its local cache. 
Reply all
Reply to author
Forward
0 new messages