New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
next.config.js
is not considered for node_modules that import next/image
#31065
Comments
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. |
While investigating a similar issue (see #33228) I've found that the |
I am having this exact issue. What's especially odd is that, when I run It is also not an issue when I do a build and run in production mode; it only happens in development mode. |
@styfle have you found any temporary workarounds for the time being? |
Theres a PR you could try out: #33559 |
Hi @styfle - just curious, any anticipated release milestone for this fix? |
We'll have it for 12.1.0. The work is being done in PR #33559 |
This was released in 12.0.11-canary.10. You can try it out today with |
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. |
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 importsnext/image
:Expected Behavior
Should read the
next.config.js
properly, even for 3rd party packages insidenode_modules
that importnext/image
To Reproduce
https://github.com/pacocoursey/next-image-bug
The text was updated successfully, but these errors were encountered: