Cyril Wanner

Yes, this limitation comes from the babel plugin. I'll have to extend that so it correctly recognizes this use-case.

@mehmetnyarar the code you have posted should work as you expect it to work. If the solution which @dosentmatter posted does not work, can you share a minimal reproduction example...

@antontsvil You define the `webpack` function twice in your file (once with the css plugin and once at the bottom) and the way `next` works, they overwrite each other so...

Ah, I see. The config gets passed to the plugins before they run so they are aware of the values set there (e.g. the `publicPath` etc). I think your current...

I tried it in a new project with the current next.js version and can not see this output. Can you post your next.config.js file (maybe it is coming from another...

The upcoming major version (v3, currently in the [canary](https://github.com/cyrilwanner/next-optimized-images/tree/canary) branch) provides an [Svg](https://github.com/cyrilwanner/next-optimized-images/tree/canary#svg) component which I think is exactly what you want. However, it uses a `span` tag as a...

This is a planned feature of the next major version (#120), but I haven't started on that particular feature yet. So until that feature is out, I think your solution...

I published a new canary version today which should recognize more use-cases (also styled-components) so I suggest trying that out. A missing babelrc setting could also lead to this error....

@JannikZed there was indeed a wrong typing in the `Svg` component, thank you very much for reporting it! The version `3.0.0-canary.8` should fix this problem. @LucasMallmann The typing of the...

Hi @mrgoonie I see in your `package.json` that you have `imagemin-optipng` and `imagemin-pngquant` installed. I'm not sure, but this could be the reason that next-optimized-images gets confused because of that....