Cache folder isn't created when using (Image Component) + SVG images

[StarpTech]

Bug report

Describe the bug

According to https://nextjs.org/docs/basic-features/image-optimization#caching Next.js populates a cache dir when using the new <Image /> component. This is not the case when using SVG files. This results in a performance penalty.

To Reproduce

1. Use the new <Image /> component in combination with an SVG image.
2. Build for production npm run build
3. Start your app npm start
4. Visit the page
5. Check <distDir>/cache/images
6. No files have been generated!

Expected behavior

I'd expect to see the generated files in the cache directory. Even when the files can't be optimized the files should be served from the filesystem on subsequent calls.

System information

• OS: Ubuntu
• Browser (if applies) chrome
• Version of Next.js: 10.0.1
• Version of Node.js: 12.19.0

[kaykdm]

I can reproduce this issue with "next": "10.0.4",
It is not only svg but also animated images are not cached

@timneutkens
Can I take this issue?
The fix would be to cache svg and animated images, right?

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.