Webpack code-splitting produce wrong chunks paths

Preflight Checklist

• [x ] I have read the contribution documentation for this project.
• [ x] I agree to follow the code of conduct that this project follows, as appropriate.
• [x ] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

• Electron Forge Version:
  • 6.0.0-beta.50
• Electron Version:
  • 8.2.1
• Operating System:
  • macOS 10.15.4

Expected Behavior

Webpack code chunks are resolved and loaded successfully in production mode

Actual Behavior

Webpack code chunks cannot be resolved and loaded in production mode (but in dev it works)

To Reproduce

• use react lazy-loading in your app (for example, make some /page route lazy-loading)
• use webpack config without optimisation preferences
• run electron-forge package
• check out/name.app/Resources/app/.webpack/renderer folder.
• See main_window/index.jsthere - it’s an entry point of the app
• See 1/index.js there - as I understand, it’s a chunk of our splitted route
• Run built app
• Go to /page route
• Observe 404 error in console - it tries to load renderer/main_window/1/index.js instead of renderer/1/index.js

[sebastianwd]

I think I managed to make it work. I added this to my webpack.renderer.config.js

output: { chunkFilename: 'main_window/[name].chunk.js', publicPath: '../', },

So what this does is create the files in the main_window directory entry, this alone would make webpack search for the file main_window/main_window/0.chunk.js and return 404. So I added the publicPath property to search outside that directory and make the paths coincide.

[ianpogi5]

@sebastianwd Thank you very much!