strange inline data uris with next 6

Hi @cyrilwanner this is a great idea, but having some issues getting it working. My inline images are being generated with data uris like this:

data:image/png;base64,bW9kdWxlLmV4cG9ydHMgPSBfX3dlYnBhY2tfcHVibGljX3BhdGhfXyArICJkMzI1YWI2YzI3ZWEyYzg5NzRmNGMyYjQ5MDI2NGE4YS5wbmciOw==

which, when decoded, contains text content like this:

module.exports = __webpack_public_path__ + "d325ab6c27ea2c8974f4c2b490264a8a.png";

which clearly isn’t an image. Is this an incompatibility with next 6 situation I’m encountering here?

Any help appreciated!

fyi. just using imagesFolder and imagesPublicPath config keys.

[notatestuser]

Oops, it was the file-loader. we have quite a large next.config.js and it was hiding down at the bottom. sorry for the false alarm and I can confirm that it’s now working as intended. 😄

There still seems to be an issue with a jest test breaking due to an image but that’s a different topic.

[notatestuser]

Wait, I think I might have found what is doing it-

config.module.rules.push({
  test: /\.(ico|gif|png|jpg|jpeg|svg|webp|eot|ttf|woff|otf)$/,
  use: [
    'file-loader',
  ],
});

let me remove this and see what happens.