Statically imported image in Next 16.2 (Pages Router) breaks ‎`next dev` in Safari 26.4

[lsvs]

Link to the code that reproduces this issue

https://github.com/lsvs/next-16.2-statically-imported-image-bug-safari-reproduction-pages

To Reproduce

1. Start the app in development mode with ‎next dev.
2. Open the app in Safari 26.4 on macOS Sequoia.
3. The page immediately crashes with the runtime error:

   Runtime Error
   Image with src "/_next/static/media/image.3_pmqoemjixc0.png?ts=..." is using a query string which is not configured in images.localPatterns.

Current vs. Expected behavior

Current behavior:

In Safari 26.4, a statically imported image used with the Pages Router in Next 16.2.1-canary.13 crashes the page in development with an error about a query string not being configured in ‎images.localPatterns. The same code runs without issue in Chrome and Firefox.

Expected behavior:

A statically imported image should work out of the box with the Pages Router in development, without requiring any ‎images.localPatterns configuration, and should behave consistently across browsers (Safari, Chrome, Firefox).

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.6.0: Fri Feb 27 19:30:16 PST 2026; root:xnu-11417.140.69.709.8~1/RELEASE_ARM64_T8112
  Available memory (MB): 24576
  Available CPU cores: 8
Binaries:
  Node: 22.22.0
  npm: 11.11.0
  Yarn: 1.22.22
  pnpm: 10.33.0
Relevant Packages:
  next: 16.2.1-canary.13 // Latest available version is detected (16.2.1-canary.13).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Image (next/image), Pages Router

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

I tested the reproduction against:

• 16.1.7 → works as expected
• 16.2.x (including ‎16.2.1-canary.13) → bug is present

This appears to be a regression introduced between 16.1.7 and 16.2.x.

• The issue is reproducible locally on macOS Sequoia.
• It only happens in Safari; Chrome and Firefox work fine with the same dev server and code.
• The reproduction uses a statically imported image in a Pages Router page without additional ‎next.config.js image configuration.

[finessor06]

Hey mate — if you’re still stuck, I can help you debug this. Just head over to my debugging‑service repo and open an Issue. All the steps are in the README, so you’ll know exactly what to include. Thank you.

[christopherjohnson3028-stack]

Thanks for reaching out.

…

On Mon, Mar 30, 2026, 10:45 PM finessor06 ***@***.***> wrote: *finessor06* left a comment (vercel/next.js#92118) <#92118 (comment)> Hey mate — if you’re still stuck, I can help you debug this. Just head over to my debugging‑service repo and open an Issue. All the steps are in the README, so you’ll know exactly what to include. Thank you. — Reply to this email directly, view it on GitHub <#92118?email_source=notifications&email_token=B67D5GLDLMBV7EENHF7W7J34TM5L3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJVHE3DMMRZGUZKM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4159662952>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B67D5GPDZ2DSFEDBLYPOZ3T4TM5L3AVCNFSM6AAAAACXGXRMWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNJZGY3DEOJVGI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[victorlangston123-droid]

I am seeing the same runtime error regarding images.localPatterns when using statically imported images in Next 16.2.1-canary.13. On Tue, Mar 31, 2026, 8:40 AM christopherjohnson3028-stack < ***@***.***> wrote:

…

*christopherjohnson3028-stack* left a comment (vercel/next.js#92118) <#92118 (comment)> Thanks for reaching out. On Mon, Mar 30, 2026, 10:45 PM finessor06 ***@***.***> wrote: > *finessor06* left a comment (vercel/next.js#92118) > <#92118 (comment)> > > Hey mate — if you’re still stuck, I can help you debug this. Just head > over to my debugging‑service repo and open an Issue. All the steps are in > the README, so you’ll know exactly what to include. Thank you. > > — > Reply to this email directly, view it on GitHub > < #92118?email_source=notifications&email_token=B67D5GLDLMBV7EENHF7W7J34TM5L3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJVHE3DMMRZGUZKM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4159662952>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/B67D5GPDZ2DSFEDBLYPOZ3T4TM5L3AVCNFSM6AAAAACXGXRMWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNJZGY3DEOJVGI> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > — Reply to this email directly, view it on GitHub <#92118?email_source=notifications&email_token=CAXXQK5XLOOFK3Q4775PZBT4TPDEDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJWGI3TENJZGU42M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4162725959>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CAXXQK3IRZ2HGODXLEMM4W34TPDEDAVCNFSM6AAAAACXGXRMWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNRSG4ZDKOJVHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>