Skip to content
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] Image Optimization for default loader #5321

Merged
merged 1 commit into from Oct 24, 2020

Conversation

styfle
Copy link
Member

@styfle styfle commented Oct 24, 2020

We currently pass through images whenever its defined, but this is enabling Image Optimization in the Proxy for every Next.js project.

Instead, we should check to see if the default loader is used (the same use for next dev) as a signal to enable this feature in the deployment.

Related to vercel/next.js#18122

@kodiakhq kodiakhq bot merged commit 21df39f into master Oct 24, 2020
@kodiakhq kodiakhq bot deleted the next-disable-image-optimization branch October 24, 2020 12:55
kodiakhq bot pushed a commit to vercel/next.js that referenced this pull request Oct 25, 2020
We currently always accept requests to the new `/_next/image` endpoint, even when it should not be used.

Instead, we should check to see if the default loader is used as a signal to enable this API.

Other loaders (such as cloudinary) will not go through the Next.js API so there is no need to expose this, instead we 404.

- Analogous to vercel/vercel#5321
- Related to #18122
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.

None yet

3 participants