Skip to content

Upgrade to Next.js 16.2.1#786

Merged
miurla merged 1 commit intomainfrom
chore/next-16-2-upgrade
Mar 21, 2026
Merged

Upgrade to Next.js 16.2.1#786
miurla merged 1 commit intomainfrom
chore/next-16-2-upgrade

Conversation

@miurla
Copy link
Copy Markdown
Owner

@miurla miurla commented Mar 21, 2026

Summary

  • upgrade Next.js to 16.2.1 and align eslint-config-next/eslint versions
  • migrate from legacy .eslintrc to ESLint flat config for Next.js 16
  • fix hydration mismatches introduced during the upgrade while keeping react-hooks/set-state-in-effect enabled

Validation

  • bun lint
  • bun run typecheck
  • bun run test
  • bun format:check
  • bun run build

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 21, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
morphic Ready Ready Preview, Comment Mar 21, 2026 8:42am

@miurla miurla merged commit a497ef9 into main Mar 21, 2026
8 checks passed
@miurla miurla deleted the chore/next-16-2-upgrade branch March 21, 2026 08:43
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4666662f4f

ℹ️ 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".

Comment on lines +97 to 98
if (state.key === normalizedKey) {
return
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Retry unchanged image sets after preload failures

When every window.Image() preload fails once (for example because the remote host briefly times out), setState still records state.key = normalizedKey. This early return then skips all future preload attempts for the same images prop, so a rerender of the same search result stays stuck in the empty state and shows No images found until the component is remounted or the query changes. That makes transient image/CDN failures permanent for the lifetime of the message.

Useful? React with 👍 / 👎.

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.

1 participant