Open MichaelJCole opened 1 year ago
Thanks for your suggestion. It is really necessary to add an example using ipc in the template. Of course you can get more in the documentation.
About sandbox:
Read more in Limitations of Sandboxing
Nuxt has nuxt-vite but is abandoned. Now has nuxt-bridge which should support vite, maybe not only for old projects. Nuxt 4 is in the making, but maybe more official template(nuxt or create-electron-vite) with healthy default ipc settings is needed but a lot of electron-nuxt templates vanished into void and official seems problematic due a lot of trash untypical for Nuxt and so some tb tnt appears
Clear and concise description of the problem
Hi, I'm looking to integrate nuxt with electron. I'm coming from the Quasar project. Quasar uses electron-vite.
I started with
nuxt-electron
plugin, but it disables a bunch of security features in electron.This is the most secure config I could get to get the example started.
I'm coming from Quasar, which appears to use electron-vite. The most secure config I can get is:
So why not use electron-vite directly? The most secure config I can get seems to be with the sandbox turned off:
If I enable the sandbox content doesn't show in the vue-typescript version. This seems to be the default for quickstart and electron-vite-boilerplate
What is Quasar doing with electron-vite to allow enabling the sandbox? Quasar appears to install electron-vite here and only needs to turn off sandbox to use @electron/remote
I don't see @electron/remote in the quick-start, why is
sandbox: false
needed?Thank you!
Used Scaffolding
create-electron
Suggested solution
Use IPC in the examples.
Alternative
No response
Additional context
No response
Validations