-
Notifications
You must be signed in to change notification settings - Fork 24
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
add netlify handler #96
Conversation
Issue #71 seems to be impacting this, otherwise everything looks good to go! When yarn linking with |
38cb9e6
to
69d0beb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good! Left a few remarks, also please also run yarn gendocs
and commit the changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, please add netlify to the exports map in the package.json
.
@enisdenjo I'm seeing a weird issue where the compiled .mjs files have |
b98b4ff
to
db14972
Compare
Have you tried cleaning/removing the lib directory and then building again? |
@enisdenjo yup, that does the trick! should I add to the example a step to detect http method and error on anything besides |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also rebase. Note that I've pushed the lighthouse readme changes on the main branch. So this PR should have a smaller changeset afterwards.
2d1863c
to
53897b1
Compare
8768212
to
23bab49
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@enisdenjo haha, can relate with the PR traffic. rebased, thanks so much! |
Not really sure what happened, but the lighthouse change is still in this PR while the same is already on main (ef8b311). Have you pulled main first? |
You're missing 9 commits from the |
@enisdenjo ahhh, I'm not used to working from forks. i rebased from origin (my fork) and not upstream |
weird, after rebasing and locally squashing, and running also it seems something with the github cache failed with something related to a lighthouse docker image |
@enisdenjo it is rebased off the latest upstream I already pulled it into our netlify function directly and it works great |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is it, great work @acao and thanks!
thanks @enisdenjo, it's been great working with you, and working in this repo is really nice! |
🎉 This PR is included in version 1.21.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
use
implementation (for review)