I've met the same problem as was described in this issue #22. I investigated a little and found that this error occurs when, due to some reasons, package is missing the main file.(was not compiled properly after install or some raise conditions e.t.c.)
This fix returns appropriate error message that informs about that. I think this is more expected behaviour than just failure with no additional info.
Passing error message when main file from package.json is not found
fixed in 0.4.1.