This repository was archived by the owner on Mar 14, 2020. It is now read-only.
bring lighthouse-lambda up to node 12 and lighthouse 5.6 #37
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Hi @AlanSwenson , thanks for all your efforts. Unfortunately, we do not actively maintain this project at the moment. Feel free to fork it to another repository with your changes. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since 8.10 is no longer available on AWS, this update brings the project up to Node10/12 as well lighthouse version 5.6.
Also updates vulnerable npm packages.
the main things that are happening is swapping serverless for chrome-aws-lambda and using await.
I have updated the test as well, but probably needs further testing.
Also still needs Readme updates. If you intend to merge this I will write that as well.