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

chore: update lighthouse #183

Merged
merged 2 commits into from
Feb 2, 2024
Merged

Conversation

lutejka
Copy link
Contributor

@lutejka lutejka commented Jan 25, 2024

Description

Hey @harlan-zw this will update lighthouse to the current version. I already gave it a try in #167 but it did not play nice with jiti However, this time it seems to work fine for me. If it does not work for you, let me know, so I can investigate further.

Linked Issues

#124

@lutejka
Copy link
Contributor Author

lutejka commented Jan 25, 2024

The test is failing because the best-practice score is below the budget.
[Unlighthouse] /blog/2023-may has invalid score 0.74for categorybest-practices`
I updated the budget, but the test still seem to use the old budget. Not sure to rerun them with the current budget

@harlan-zw
Copy link
Owner

Thanks, I'm guessing this may have some issues but will merge anyway and try to get this shipped 🚢

@harlan-zw harlan-zw merged commit 18dfa53 into harlan-zw:main Feb 2, 2024
1 check failed
@harlan-zw
Copy link
Owner

Actually looks to be working pretty well! I think JITI finally solved their blocking issue with the CJS / MJS

@lutejka lutejka deleted the lighthouse-update branch February 3, 2024 10:55
@lutejka
Copy link
Contributor Author

lutejka commented Feb 3, 2024

The trick is actually to add the .cjs extension to the import. This will tell node how to interpret the import...

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

Successfully merging this pull request may close these issues.

2 participants