Jeff Robbins

> Environment variables are currently the preferred solution. Fair enough.

Your link doesn't seem to work for some reason. You're saying that [this issue](https://github.com/herberttn/bytenode-webpack-plugin/issues/15) has re-emerged on Windows in the current version (2.3.1)? I wrote a [source code leak test](https://github.com/spaceagetv/electron-bytenode-example/blob/main/test/code-leaks.spec.ts)...

I just added some automated testing to the [electron-bytenode-example](https://github.com/spaceagetv/electron-bytenode-example) project and I cannot replicate this bug for Windows, Linux, or Mac… at least for an Electron build. I can't speak...

Source maps would be very cool! Though we should certainly default to disabling them… and explaining to people clearly why they might want to keep them disabled.

Source maps would be very cool! Though we should certainly default to disabling them… and explaining to people clearly why they might want to keep them disabled.

I think I may have just put that test in to see if text strings were making it through. It makes sense that they would be. Maybe a better test...

First, thanks for the PR! It looks like the tests aren't passing due to errors like this: ``` ERROR in ./node_modules/bytenode/lib/index.js 3:15-39 Module not found: Error: Can't resolve 'assert' in...

Still just experimenting, but here's an Electron Fiddle example of sending the entire `Menu.getApplicationMenu()` via IPC. It's interesting to see the structure: https://gist.github.com/jjeff/275161cf15af794b7f0fdbd22709e747

Thanks. However, doesn't this example still use @electron/remote? https://github.com/6c65726f79/custom-titlebar/wiki/Advanced-examples#use-without-electronremote I've been working on an updated version. It successfully sends the Menu system to the renderer. It successfully finds the MenuItem...

> @jjeff @6c65726f79 any update on this? Were you able to make it work? I gave up and went back to native menus. 😕