aws-lambda-image icon indicating copy to clipboard operation
aws-lambda-image copied to clipboard

Error when running npm run deploy

Open user23145 opened this issue 7 years ago • 4 comments

After running sudo npm run deploy (Amazon Linux), I get the following error output:

> [email protected] deploy /home/ec2-user/aws-lambda-image
> claudia create --profile $npm_package_config_profile --region $npm_package_config_region --version dev --handler index.handler --no-optional-dependencies --timeout $npm_package_config_timeout --memory $npm_package_config_memory --policies policies/*.json

Source directory is the Node temp directory. Cowardly refusing to fill up disk with recursive copy.

npm ERR! Linux 4.9.32-15.41.amzn1.x86_64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "deploy"
npm ERR! node v6.11.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] deploy: `claudia create --profile $npm_package_config_profile --region $npm_package_config_region --version dev --handler index.handler --no-optional-dependencies --timeout $npm_package_config_timeout --memory $npm_package_config_memory --policies policies/*.json`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] deploy script 'claudia create --profile $npm_package_config_profile --region $npm_package_config_region --version dev --handler index.handler --no-optional-dependencies --timeout $npm_package_config_timeout --memory $npm_package_config_memory --policies policies/*.json'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the aws-lambda-image package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     claudia create --profile $npm_package_config_profile --region $npm_package_config_region --version dev --handler index.handler --no-optional-dependencies --timeout $npm_package_config_timeout --memory $npm_package_config_memory --policies policies/*.json
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs aws-lambda-image
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls aws-lambda-image
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ec2-user/aws-lambda-image/npm-debug.log

What am I doing wrong?

user23145 avatar Jul 14 '17 02:07 user23145

I'm getting the same error

Windows 10 node v6.11.2 npm v3.10.10

stormcrow85 avatar Aug 13 '17 20:08 stormcrow85

This might help you. You have to set TMPDIR env var as described here: https://github.com/ysugimoto/aws-lambda-image/issues/125

mhuebner avatar Aug 14 '17 16:08 mhuebner

Hi, thanks for the response. I was able to run Claudia without setting TMPDIR, like so:

"deploy": "claudia create --profile $npm_package_config_profile --region $npm_package_config_region --version dev --handler index.handler --no-optional-dependencies --timeout $npm_package_config_timeout --memory $npm_package_config_memory --policies policies/*.json"

But it seems that I have a different problem, it seems that $npm_package_config_VARNAME vars are undefined, so currently "npm run deploy" breaks because claudia create has no arguments. My package.json file is identical to the latest repository version

Replacing the $npm_package_config values in package.json with the actual values does work. But I still wonder why would the vars be ignored.

Thanks for any insight on this

stormcrow85 avatar Aug 14 '17 22:08 stormcrow85

I have this problem using migrating from node 14 to node 16

fabianobonomini avatar Jun 10 '23 18:06 fabianobonomini