-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task "lambda_package" not found. #22
Comments
Could you post your Gruntfile.js and package.json? That might help determine whether it's an implementation issue or an issue with the actual plugin. |
Sure thing, pretty basic content. I've attached both for your review. It seems that part of it is that grunt-cli changed to have deploy be the alias for both package and deploy. Also, even running grunt --help I get errors with "Loading 'Lambda_package.js' tasks..." Looks like it might be having an issue not finding npm as well. Gruntfile.js
package.json
|
I think |
The issue not finding npm sounds a lot like #20. That one would result in the same sort of errors for me. |
This issue happens because the task is failing due to an error. It's looking for the |
That would be great if I was on a Linux system, but I’m on windows…and end up with a bunch of nested directories that are almost impossible to get rid of. From: goliatone [mailto:notifications@github.com] This issue happens because the task is failing due to an error. It's looking for the npm package and is not found. — |
@jasonfreier You can upgrade to npm 3, which flattens dependency structures, by running |
After uninstalling and reinstalling dependencies and grunt-aws-lambda 0.8.0, packaging no longer works for me. Prior to this version it was working even with the default empty lambda_package setting in Gruntfile.js.
Grunt 0.4.5
Grunt-Cli 0.1.13
Grunt-aws-lambda 0.8.0
The text was updated successfully, but these errors were encountered: