volo fails silently

[Worik Stanton]

Friends

I have two ubuntu machines.  Both 12.10

I installed nodejs according to https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager and installed volo via sudo npm install -g volo on both machines.

Running volo create fos-todo-app  creates a (as yet untested) project on one of my machines (the desktop) and does nothing, silently on the other (the laptop)

On the laptop I removed:

 ~/.npm, /usr/local/bin/volo,  /usr/local/lib/node_modules/ and /usr/bin/volo and repeated the installation as above.  Still silent failure.


Following the instructions at https://github.com/volojs/volo/blob/master/docs/workingWithCode.md I installed  node-inspector via npm

node --debug-brk `which volo` create  fos-todo-app

fails silently.

I am out of options. 

How can I get some indication of what is wrong with volo on the laptop?

cheers
Worik

[James Burke]

When you do this command:

node --debug-brk `which volo` create fos-todo-app

Does it stop in the debugger first, or fail immediately? If it fails
immediately, then it sounds like a problem with the installation that
npm did for volo, or perhaps a PATH issue finding the volo script?

I would confirm that `which volo` gives a path to a real file, and I
would ls -la on that path to make sure that if it is a symlink, that
it goes to a real file that can just be loaded directly with node.

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

[Worik Stanton]

On Friday, 28 June 2013 07:30:04 UTC+12, James Burke wrote:

When you do this command:

node --debug-brk `which volo` create  fos-todo-app

Does it stop in the debugger first, or fail immediately? If it fails
immediately, then it sounds like a problem with the installation that
npm did for volo, or perhaps a PATH issue finding the volo script?

It fails immediately.

 

I would confirm that `which volo` gives a path to a real file, and I
would ls -la on that path to make sure that if it is a symlink, that
it goes to a real file that can just be loaded directly with node.

worik@noam:~/public_html$ ls `which volo` -l
lrwxrwxrwx 1 root root 33 Jun 27 12:40 /usr/bin/volo -> ../lib/node_modules/volo/bin/volo
worik@noam:~/public_html$ ls /usr/lib/node_modules/volo/bin/volo -l
-rwxr-xr-x 1 nobody worik 1149 Jun  6 07:51 /usr/lib/node_modules/volo/bin/volo
worik@noam:~/public_html$

I will have a fresh look today.

It would be helpful to know what I should have deleted to get back to a clean slate. 

Did I leave any nodejs or volo files around?

Also is there any documentation for these tools?  I am very new to them (not new to programming).
cheers
Worik

[James Burke]

Response inline below:

On Thu, Jun 27, 2013 at 2:05 PM, Worik Stanton <worik....@gmail.com> wrote:
> worik@noam:~/public_html$ ls `which volo` -l
> lrwxrwxrwx 1 root root 33 Jun 27 12:40 /usr/bin/volo ->
> ../lib/node_modules/volo/bin/volo
> worik@noam:~/public_html$ ls /usr/lib/node_modules/volo/bin/volo -l
> -rwxr-xr-x 1 nobody worik 1149 Jun 6 07:51
> /usr/lib/node_modules/volo/bin/volo
> worik@noam:~/public_html$
>
> I will have a fresh look today.
>
> It would be helpful to know what I should have deleted to get back to a
> clean slate.
>
> Did I leave any nodejs or volo files around?
>
> Also is there any documentation for these tools? I am very new to them (not
> new to programming).
> cheers

That looks OK on the surface of it, but we are not getting into areas
where I am less experienced. This seems to be a node/npm install
issue, so resources that may help:

For node:

http://nodejs.org/docs/

then choose the link for the version of node you have installed.

For npm, this is the main source repo:
https://github.com/isaacs/npm

The readme may have some hints. The docs:
https://npmjs.org/doc/

and faq:
https://npmjs.org/doc/faq.html

may be useful.

James