next.config.js is not considered for node_modules that import next/image

[styfle]

What version of Next.js are you using?

12.0.3

What version of Node.js are you using?

16.x

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

next start

Describe the Bug

Getting an error during next dev when a dependency imports next/image:

Error: Invalid src prop (https://i.imgur.com/CgezKMb.jpg) on next/image, hostname "i.imgur.com" is not configured under images in your next.config.js
See more info: https://nextjs.org/docs/messages/next-image-unconfigured-host

Expected Behavior

Should read the next.config.js properly, even for 3rd party packages inside node_modules that import next/image

To Reproduce

https://github.com/pacocoursey/next-image-bug

[styfle]

Some additional context: this is not just relevant for 3rd party packages published to npm, but also monorepos using workspaces or private packages shared between projects.

[johnnyomair]

While investigating a similar issue (see #33228) I've found that the next.config.js is also not considered when using the next/image component in a 3rd party package in combination with the priority flag.

[trevorgillis]

I am having this exact issue. What's especially odd is that, when I run next dev, I get the error and my app doesn't load (as expected and stated in the issue). If I then, in my Next.js app, temporarily comment out the third-party code that's using next/image and reload, it loads without the error (as expected). But then, while the dev server is still running, if I uncomment the third-party code that's using next/image, it works.

It is also not an issue when I do a build and run in production mode; it only happens in development mode.

[trevorgillis]

@styfle have you found any temporary workarounds for the time being?

[styfle]

Theres a PR you could try out: #33559

[ambrauer]

Hi @styfle - just curious, any anticipated release milestone for this fix?

[styfle]

We'll have it for 12.1.0.

The work is being done in PR #33559

[styfle]

This was released in 12.0.11-canary.10.

You can try it out today with npm i next@canary or yarn add next@canary, thanks!

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.