chore(docs): add docs for .svg unoptimized behavior
#60735
Conversation
styfle
requested review from
timneutkens,
ijjk,
shuding,
huozhi,
ztanner and
a team
as code owners
styfle
requested review from
jh3y and
StephDietz
and removed request for
a team
ijjk
added
area: documentation
created-by: Next.js team
| If you need to serve SVG images with the default Image Optimization API, you can set `dangerouslyAllowSVG` inside your `next.config.js`: | ||
| Therefore, we recommended using the [`unoptimized`](#unoptimized) prop when the [`src`](#src) prop is known to be SVG. This happens automatically when `src` ends with `".svg"`. | ||
|
|
||
| However, if you need to serve SVG images with the default Image Optimization API, you can set `dangerouslyAllowSVG` inside your `next.config.js`: |
There was a problem hiding this comment.
Should we also mention the dangerouslyAllowSVG option in the images next.config.js page? https://nextjs.org/docs/app/api-reference/next-config-js/images
It would be good to mention all the keys for the images option on this page.
There was a problem hiding this comment.
Feels like we just need stronger SVG guidance: shouldn't be used with next/image?
That removes the config option entirely.
There was a problem hiding this comment.
There are use cases where you might want svg to be cached and served from the same domain if the svg images are external urls. Although you can probably use rewrites for this.
I think the word "dangerous" in the property name is pretty good guidance already.
Regardless, that doesn't answer @delba's question/suggestion 😅
Co-authored-by: Delba de Oliveira <[email protected]>
Closes NEXT-2119