Wrongly placed query parameters

[blitzbohne]

Hi!

As soon as we start to use next optimized images (which works fine btw.) and we, for example use ?resize on a png image somewhere it starts to do the SAME for all images like also svg images which of course then results in ./static/pages/website/company/hero.svg?resize which throws errors.

We did NOT setup any default queries in the config so this should not happen right?

[cyrilwanner]

Hi @alpfactory-alex
Yes, this sounds strange and should definitely not happen. Can you share a bit more information about your project? E.g. node version, next version, next-optimized-images version and do you have other plugins or a custom webpack configuration in place? Thanks already!

[lasersox]

@cyrilwanner I have this same problem. Using next.js v9.0.1. Here's my next.js config:

const withPlugins = require('next-compose-plugins');
const optimizedImages = require('next-optimized-images');

module.exports = withPlugins(
  [
    [
      optimizedImages,
      {
        inlineImageLimit: 16384,
        mozjpeg: {
          quality: 95
        }
      }
    ]
  ],
  {
    webpack: cfg => {
      cfg.module.rules.push({
        test: /\.md$/,
        use: 'frontmatter-markdown-loader'
      });
      return cfg;
    }
  }
);

I have this issue when using next export

[cyrilwanner]

@lasersox sorry for the late reply. Is it possible to provide a minimal reproduction example? It looks like this is very project-specific and I couldn't reproduce it yet.