You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 14, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 14, 2020. It is now read-only.
@dordax this workaround 'almost' works for me but now I get a bunch of warn Caught exception: NO_TRACING_STARTED for each type of audit and the final report is just filled with errors instead of the data. My lambda works fine on 8.10 but just wanted to upgrade to keep with the times. Anything you changed in your handler function to go from 8.10 -> 12?
if anyone else runs into this issue trying to use node 12, I did what @dordax did but I needed to remove '--single-process' to get the performance tests on lighthouse to stop returning errors
Well consider 8.10 is now in maintenance (https://nodejs.org/en/about/releases/) this should probably be updated. I have a fork Im working on, if it works for me I'll open a PR.
@smcelhinney did you get it working?
I forked it a few weeks ago and changed a lot of things and got it working on node 12 on the local docker AWS instance but could never get it going on the actual lambda.
Activity
trevsewell commentedon Dec 8, 2019
I'm getting the same thing with 3.1.1
kevsersrca commentedon Dec 13, 2019
Same as my error, getting runtime lambda nodejs 10.x and 12.x . but working runtime nodejs8.10
brandysnaps commentedon Dec 18, 2019
I'm seeing the same issue. Working fine for
8.10but not10.xor12.x.dordax commentedon Jan 17, 2020
I've made a quick workaround using this lib instead @serverless-chromium: https://github.com/alixaxel/chrome-aws-lambda.
Works with 10.x and 12.x.
npm install chrome-aws-lambda --save-prodIn https://github.com/joytocode/lighthouse-lambda/blob/master/lib/index.js:
AlanSwenson commentedon Jan 31, 2020
@dordax this workaround 'almost' works for me but now I get a bunch of
warn Caught exception: NO_TRACING_STARTEDfor each type of audit and the final report is just filled with errors instead of the data. My lambda works fine on 8.10 but just wanted to upgrade to keep with the times. Anything you changed in your handler function to go from 8.10 -> 12?AlanSwenson commentedon Jan 31, 2020
if anyone else runs into this issue trying to use node 12, I did what @dordax did but I needed to remove
'--single-process'to get the performance tests on lighthouse to stop returning errorssmcelhinney commentedon Feb 26, 2020
Well consider 8.10 is now in maintenance (https://nodejs.org/en/about/releases/) this should probably be updated. I have a fork Im working on, if it works for me I'll open a PR.
AlanSwenson commentedon Feb 28, 2020
@smcelhinney did you get it working?
I forked it a few weeks ago and changed a lot of things and got it working on node 12 on the local docker AWS instance but could never get it going on the actual lambda.
smcelhinney commentedon Feb 28, 2020
I gave up on Lambda and moved my code to Google Cloud Run and Pub Sub topics :)
AlanSwenson commentedon Mar 12, 2020
I finally have a working solution in #37