npm run install-all fails, then just plain old npm install fails

[julian45]

sudo npm run install-all gives:

npm ERR! Linux 3.13.0-74-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "install-all"
npm ERR! node v6.1.0
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR! @jimpick/lambda-comments@0.0.1 install-all: `npm install && cd packages/frontend && npm install`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @jimpick/lambda-comments@0.0.1 install-all script 'npm install && cd packages/frontend && npm install'.
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 @jimpick/lambda-comments package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm install && cd packages/frontend && npm install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs @jimpick/lambda-comments
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls @jimpick/lambda-comments
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/lambda-comments/npm-debug.log

sudo npm install on its own gives:

npm ERR! Linux 3.13.0-74-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v6.1.0
npm ERR! npm  v3.8.6                                                                      npm ERR! code E404

npm ERR! 404 Not found : @jimpick/akismet-api
npm ERR! 404                                                                              npm ERR! 404  '@jimpick/akismet-api' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of '@jimpick/lambda-comments'               npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/lambda-comments/npm-debug.log

Something tells me that this may have to do with the recent security upgrade to 6.x and the apparent phasing-out of 5.x.

[julian45]

Also, your README specifies some stuff with Lambda and 4.3 - due to current needs, I can't downgrade to 4.x.

[jimpick]

Looks like it's failing on the scoped package I published: @jimpick/akismet-api

Funny, I tried an 'npm install' here, and I didn't get that error.

It had a workaround for some webpack issues I encountered. If I fix issue #3, I won't need the scoped package.

[jimpick]

Node 4.3 is the version that it runs on inside Amazon's cloud. I've been developing with a newer version with no problem.

[julian45]

Huh. That's interesting; Lemme try grabbing nvm and seeing if I can (for some inexplicable reason) install from 4.x.

[julian45]

Nope, still fails. Should I try reinstalling when #3 is fixed?

[jimpick]

I've upgraded akismet-api so there's no need for the scoped package anymore. Can you try again to see if that makes your problem go away?

[julian45]

Seems to go fine now! However, I get warned with the following:

npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.

As a safety, I ran sudo npm install pug. It also said something related to fsevents being incompatible, but due to the fact that I'm doing this on a Linux machine, that always happens.

[chrisfosterelli]

@tcby45 mocha uses those two dependencies. They won't upgrade them yet, as it breaks Node 0.8 support. See here and here if you want to add your voice. The next release of Mocha will have those fixed.

In the meantime though, those warnings won't cause any problems. You can use npm install --production which won't produce those warnings.

[julian45]

Alright. On another note, sudo npm run flip-lambdas-to-4.3 fails, producing the following output:

> @jimpick/lambda-comments@0.0.1 flip-lambdas-to-4.3 /home/ubuntu/lambda-comment              s
> babel-node bin/flip-lambdas-to-4.3.js

Updating function QueueCommentLambdaFunction to Node 4.3
TypeError: Cannot read property 'PhysicalResourceId' of undefined
    at _callee$ (flip-lambdas-to-4.3.js:30:24)
    at tryCatch (/home/ubuntu/lambda-comments/node_modules/babel-regenerator-run              time/runtime.js:61:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/home/ubuntu/lambda-comme              nts/node_modules/babel-regenerator-runtime/runtime.js:329:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/hom              e/ubuntu/lambda-comments/node_modules/babel-regenerator-runtime/runtime.js:94:21              )
    at step (flip-lambdas-to-4.3.js:2:1)
    at flip-lambdas-to-4.3.js:2:1
    at new Promise (/home/ubuntu/lambda-comments/node_modules/core-js/modules/es              6.promise.js:193:7)
    at flip-lambdas-to-4.3.js:2:1
    at run (/home/ubuntu/lambda-comments/bin/flip-lambdas-to-4.3.js:93:16)
    at Object.<anonymous> (flip-lambdas-to-4.3.js:41:1)
TypeError: Cannot read property 'PhysicalResourceId' of undefined
    at _callee$ (flip-lambdas-to-4.3.js:30:24)
    at tryCatch (/home/ubuntu/lambda-comments/node_modules/babel-regenerator-run              time/runtime.js:61:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/home/ubuntu/lambda-comme             nts/node_modules/babel-regenerator-runtime/runtime.js:329:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/hom              e/ubuntu/lambda-comments/node_modules/babel-regenerator-runtime/runtime.js:94:21)
    at step (flip-lambdas-to-4.3.js:2:1)
    at flip-lambdas-to-4.3.js:2:1
    at new Promise (/home/ubuntu/lambda-comments/node_modules/core-js/modules/es               6.promise.js:193:7)
    at flip-lambdas-to-4.3.js:2:1
    at run (/home/ubuntu/lambda-comments/bin/flip-lambdas-to-4.3.js:93:16)
    at Object.<anonymous> (flip-lambdas-to-4.3.js:41:1)

npm ERR! Linux 3.13.0-74-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "flip-lambdas-to-4.3"
npm ERR! node v6.1.0
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR! @jimpick/lambda-comments@0.0.1 flip-lambdas-to-4.3: `babel-node bin/flip-lambdas-to-4.3.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @jimpick/lambda-comments@0.0.1 flip-lambdas-to-4.3 script               'babel-node bin/flip-lambdas-to-4.3.js'.
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 @jimpick/lambda-comments package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     babel-node bin/flip-lambdas-to-4.3.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs @jimpick/lambda-comments
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls @jimpick/lambda-comments
npm ERR! There is likely additional logging output above.

Apologies for the output being garbled from copy-and-paste; for some reason, I can't fix it.

[jimpick]

Just a guess, but I think you might have skipped the step where you run npm run save-cloudformation.

There should be a deploy/state/cloudFormation.json file before you run npm run flip-lambdas-to-4.3.

[julian45]

Nope, it's definitely there. cating it shows what I'm guessing it should (a bunch of JSON).

[jimpick]

Hmm, I wonder if you had an issue when CloudFormation ran?

In my deploy/state/cloudFormation.json, I have an entry for the QueueCommentLambdaFunction resource that looks like this:

    {
      "StackName": "lambdaComments",
      "StackId": "arn:aws:cloudformation:us-west-2:013540632128:stack/lambdaComments/f5382f40-1281-11e6-91cb-50a68a0e3256",
      "LogicalResourceId": "QueueCommentLambdaFunction",
      "PhysicalResourceId": "lambdaComments-QueueCommentLambdaFunction-6CFMIA2HEIZ4",
      "ResourceType": "AWS::Lambda::Function",
      "Timestamp": "2016-05-05T05:28:04.038Z",
      "ResourceStatus": "CREATE_COMPLETE"
    },

[julian45]

Huh, that's not there at all. There's a bunch of other stuff, but not QueueCommentLambdaFunction. I'll try sudo npm run delete-cloudformation and try a new one.

[jimpick]

Maybe check to see if something went wrong in the CloudFormation console, eg.

https://console.aws.amazon.com/cloudformation/home?region=us-west-2#/stacks?filter=active

(You might need to change the region to match where you were installing it)

[julian45]

Checked that, and with the new stack there apparently is a QueueCommentLambdaFunction created, with a Physical ID, but it doesn't show up in deploy/state/cloudFormation.json.