Michael Erskine

The recommended was forward is to use electron-forge with the webpack template, e.g. ``` yarn create electron-app my-new-app --template=webpack ```

I keep revisiting this problem to see if anyone has a fix - most recently I've been trying to add emscripten WebAssembly code to an electron-webpack app and the stderr...

>...and simply replace it with: > > ``` > const isWin = false; > ``` > > Then try again. Does it help? Sorry for the delay, yes, it does...

Is there a release on the way that incorporates the fix?

Is it still waiting on #249 being resolved?

My company tried Vite as a replacement for electron-webpack and we couldn't find a configuration that would support our product including webassembly components, background worker threads, etc. We found a...

The recommended way forward with a supported recent electron version and webpack 5 is to use the webpack template provided with electron-forge, e.g. ``` yarn create electron-app my-new-app --template=webpack ```

I don't think that electron-webpack provides an API as such and I wouldn't want to monkey-patch the electron APIs, so I usually have a little bit of code in each...

I assume that the camera position is moving and the camera far frustum is clipping the scene.