Refresh the free-tier demo and paid preview - #3
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 94480107b2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <Image | ||
| /* The bundle timestamp in `thumb` prevents stale vendored images after a refresh. */ | ||
| // eslint-disable-next-line @next/next/no-img-element | ||
| <img |
There was a problem hiding this comment.
When the unfiltered catalog renders all 400 exercises, replacing next/image with a plain <img> without loading="lazy" removes the previous component's default lazy loading. The browser can therefore request all 394 unique thumbnail assets—about 6.2 MiB—and decode hundreds of offscreen images on every initial visit, substantially increasing network usage and memory pressure. Add native lazy loading (and preferably asynchronous decoding) or retain the optimized image component with supported cache versioning.
Useful? React with 👍 / 👎.
1 participant
What changed
generated_atso refreshed images cannot remain stuck in Next's image cacheWhy
The example was using an older snapshot, the paid-tier promotion sat below all 400 cards, and unchanged asset paths allowed stale thumbnails to remain visible after a bundle refresh.
Validation
npm run build