Jovica Aleksic

I don't know about extraResources and resourcesPath, but I would rather go for the static assets folder and __static placeholder. I'm pretty sure it works that way. Check the docs...

@benrbray I just tried to reproduce, starting from scratch with electron-webpack-quick-start, but it just worked.. Here's an example repo: https://github.com/loopmode/electron-webpack-static-examples The [initial commit](https://github.com/loopmode/electron-webpack-static-examples/commit/d6114ff57f5979a26fd29982850511a73be9b3e1) basically covers your case already. This is...

@develar Embedding static assets still confuses users, and the docs don't properly cover development vs production. I'll add explanation to the docs soonish, but should we also link this issue...

Well.. basically just use react :) You still need to install it, then in renderer/index.js you can start using it etc. So.. I have a fork with a react branch....

@tbogard sure, I built a rather large application with react and electron-webpack, using three.js and rendering heavy and interactive 3D models and scenes. Also we used some native modules to...

You have a couple of options, two of them are very easy but maybe feel inconvenient, the third one needs an inconvenient one-time solution but allows you to work the...

It might seem silly that I write such a long reply instead of submitting a PR myself, but please note that I'm mostly participating here from my phone :)

I guess the good old `/.jsx?$/` should be worth a PR and harmless/nonbreaking in any and all cases.

@mustafaKamal-fe there's at least two ways to get that done. One is where you'd do the module.hot.accept method, in your `renderer/index.js`: ``` import React from 'react' import ReactDOM from 'react-dom'...

Please also revisit this after the next release - there will be a webpack config callback function, and you'll be able to mutate the config any way you like. Not...