Skip to content
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

Error when running npm run deploy #141

Open
user23145 opened this issue Jul 14, 2017 · 4 comments
Open

Error when running npm run deploy #141

user23145 opened this issue Jul 14, 2017 · 4 comments
Labels

Comments

@user23145
Copy link

user23145 commented Jul 14, 2017

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?

@stormcrow85
Copy link

I'm getting the same error

Windows 10
node v6.11.2
npm v3.10.10

@mhuebner
Copy link

This might help you. You have to set TMPDIR env var as described here: #125

@stormcrow85
Copy link

stormcrow85 commented Aug 14, 2017

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

@fabianobonomini
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants