Open jasford opened 6 years ago
This is because your webpack target is electron-renderer
so webpack assumes require
is defined.
webpack.target
(recommended)Change your webpack.target
to be web
(See next.config.js
).
nodeIntegration
Or you can enable nodeIntegration
in your WebView
/BrowserWindow
and remove the warnings by setting ELECTRON_DISABLE_SECURITY_WARNINGS
on either process.env
or the window
object.
For a full example check out https://github.com/zeit/next.js/pull/4386
Thanks for creating this! I followed the walkthrough blog post and when I run the app in development mode (
npm start
) and open the console from inside the app, I see this warning:I think this is being triggered by the live reload parts of NextJS—so I think this is more of a false-flag warning, but I would like to not just get in the habit of ignoring that warning since it would be useful to know if I accidentally introduced a security hole by loading external content outside of a ` in my actual app.
I tried turning off
nodeIntegration
since I don't need it for my app, like this:But that just got me a full-blown error in the console:
Any ideas on how to get the hot reload to run locally so this warning is not triggered and/or so we could run with
nodeIntegration: false
?