Tim

Hi Andreas, thanks for the pull request! Could you help me understand your use case a little more. Is it that your lambda function is in the root directory, but...

Thanks for the pull request! Would you mind explaining the use case you see for this a little more? Also, it looks like the unit tests could probably cover a...

Thanks for the pull request! Would you mind adding some unit tests? Also, would this affect behaviour for existing users who might have hard-coded the output package name somewhere? Do...

Is there anything more to the message? It should also display the status code and error message: https://github.com/Tim-B/grunt-aws-lambda/blob/master/utils/deploy_task.js#L130

Try running it with the --verbose flag, I think it will display the other log which is there then.

My apologies for the delay in replying to this. Would it be possible to add unit tests to demonstrate this fixes the issue? Otherwise I might break it again in...

Thanks for your research into this. I think at some point I'll just take npm's advice re. using npm programmatically: ``` If you want to use npm to reliably perform...

I figure that although you won't know the version, the CLI API should remain relatively constant - at least for most common commands. ie. npm install will probably always be...

What use case did you have in mind? For a unit test it seems simpler to just call the functions you want to test directly from a testing framework of...

Thanks for bringing this up. I can imagine this will be a complicated to resolve if you're developing on an environment that doesn't match the Lambda environment (eg. developing on...