Jovica Aleksic

Based on electron-webpack-quick-start, with some image `src/renderer/img.png`: ```javascript // src/renderer/index.js const app = document.getElementById('app'); const img = document.createElement('img'); // img.src = require('./img.png'); // does not work, [object Module] problem img.src...

@jmeinke @zlzdp Please check whether using the `.default` property helps. I am not sure what caused this change in behaviour, but I'm pretty sure it's not a change in electron-webpack...

@Maus3rSR not sure whether it's an option for your project, but you could switch from strings to actual require statements: `src={require('@your/images.png').default}`

Good to know!

You could provide custom webpack config files for main and renderer, as explained in docs, and in the config files, export a function instead of config object. That function receives...

@millimoose first of all: sorry that there hasn't been any reaction, at all, to your issue in months. As you've probably seen, issues are piling up and remain unaddressed for...

Hey @millimoose I'm still not quite sure I understand the problem :) > The difference for me is around 500MB of node_modules versus a bundled index.js with a total of...

@prcdpr so source-map and buffer-from do belong into webpack externals? Interesting - i have already recommend a couple times to simply set externals to an empty array in your custom...

Yeah the trick is to use a custom config module that exposes a function, not an object. In that case, your config function receives the already processed options object, as...

See https://github.com/electron-userland/electron-webpack/issues/420#issuecomment-753442217