Electron >=v13.0.0-beta.6 required to support sandboxed renderers
snaildos opened this issue ยท 10 comments
Versions installed:
"@electron/remote": "2.0.1",
"electron": "^17.0.0",
What I tried:
I tried to remote: "2.0.8" and the issue still persists.
I have this problem too
I have this problem too
Yeah, clearly it's a remote bug.
Regarding reproduction,
I do not have the time to create a reproduction repo,
you could check my Fifo Browser repo, and run a development environment in there.
Or maybe someone else can send a repo that isn't a whole entire browser with assets that make it hard to debug. ๐
Thanks all!
Hi,
I encountered the same problem when using @electron/remote v2.0.8 and any electron >= v14.0.0. It seems the function getContextId() in remote.js cannot find v8_util binding - getElectronBinding('v8_util') returns null:
Any ideas how to work it around?
Thanks in advance!
Hi! Thanks for adding to the issue. Please @erickzhao refer to this issue and see if they can fix this.
Hi! I believe the source of the issue is webpack 5 and it's node polyfill removed.
from https://webpack.js.org/migrate/5/:
webpack 5 does no longer include a polyfill for this Node.js variable. Avoid using it in the frontend code.
.
remote
is using process._linkedBinding
underneath which is undefined in webpack 5 builds.
The obvious solution to include fallback to webpack config doesn't work:
resolve.fallback.process = require.resolve('process'); // does no effect
as well as installing node-polyfill-webpack-plugin.
Cheers!
Hi!
I am also getting the above issue ^ any ideas?
I don't mind jumping on it if you have a direction.
:)
Hi everyone trying to contribute, thanks @freestlr , I managed to work it out looking at the previous issue, you can see this commit
QiYuTechDev/ElectronRemote@b57f771
was used to fix it, and it worked.
Thank you all for your time!
Kind regards,
Snail
I have this same error with webpack 4 and electron 20
No clue how to fix that. Going to give it another hour and then will start to remove remote from the app.