-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
fix(cache): remove cache rules from fetch() #7270
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no suggestions.
3ce64b2
to
03dbe3c
Compare
Lighthouse Results
|
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.
the content looks right to me on the preview - do we have a sense for whether or not we can truly test this prior to release? the deployments themselves dont have a cache or a new release coming in.
also, I want to keep an eye on that lighthouse - hopefully it's an outlier 87
I just ran a lighthouse test (https://pagespeed.web.dev/analysis/https-nodejs-npvr1vjpb-openjs-vercel-app-en/yc38j12yqb). I got a 96 on desktop, 73 on mobile. Although the values seemed to fluctuate |
next discussion - is this critical enough a bug to fast-track? i would default towards no |
I don't think so. |
I do think so! Blog posts are missing on production /blog/ listing which is bad. |
I'm fast tracking! |
Description
Posted by @ovflowd on Slack.
Validation
Hopefully, the preview for this should show all blog posts, and once merged, the main page should do the same.
Fixes https://openjs-foundation.slack.com/archives/CVAMEJ4UV/p1732148207813379