Skip to content

fix(dev): silence fetchPriority and i18n SSR warnings#205

Merged
wab merged 1 commit into
mainfrom
fix/dev-warnings
May 22, 2026
Merged

fix(dev): silence fetchPriority and i18n SSR warnings#205
wab merged 1 commit into
mainfrom
fix/dev-warnings

Conversation

@wab

@wab wab commented May 22, 2026

Copy link
Copy Markdown
Contributor

Closes #204

Summary

  • Pass fetchpriority lowercase on OptimizedImage so React 18.3.1 stops warning about the unknown camelCase prop (its DOM allow-list lacks fetchPriority).
  • Add remix-i18next to ssr.noExternal so useChangeLanguage shares the bundled react-i18next module instance and reads the I18nContext set by our <I18nextProvider> — eliminates the NO_I18NEXT_INSTANCE SSR warning.

Test plan

  • pnpm dev:local, hit /, /blog, /blog/:slug, /clients → no warnings
  • pnpm check green
  • pnpm typecheck green
  • pnpm test:run app/components/ui/optimized-image.test.tsx green

- Pass fetchpriority lowercase on OptimizedImage to dodge React 18.3.1's
  unknown-prop warning (its DOM allow-list lacks fetchPriority).
- Bundle remix-i18next via ssr.noExternal so useChangeLanguage shares the
  same react-i18next module (and I18nContext) as our I18nextProvider,
  eliminating the spurious NO_I18NEXT_INSTANCE warning on SSR.
@vercel

vercel Bot commented May 22, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
website Ready Ready Preview May 22, 2026 12:29pm

Request Review

@wab wab merged commit 520cb1d into main May 22, 2026
5 checks passed
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.

Silence fetchPriority and i18n SSR warnings in dev

1 participant