How to disable Electron security warnings using Webpack EnvironmentPlugin
In development, content for my electron app is served by webpack-dev-server, over localhost:8080. This triggers some noisy warnings in the JS console. I want to shut them off, because the production app won't actually be loading any content from external sources.
In main.js, I can do this:
process.env.ELECTRON_DISABLE_SECURITY_WARNINGS = true
That works great, but I don't like that this is hard-coded into the source code. I think stuff like this should be provided by the dev build process.
I've tried using webpack EnvironmentPlugin, but it doesn't have any effect.
Relevant snippet from webpack.dev.config.js
plugins: [
new HtmlWebpackPlugin(),
new MiniCssExtractPlugin(),
new webpack.EnvironmentPlugin({
'NODE_ENV': JSON.stringify('development'),
// disables electron warning about insecure content that only applies in dev scenario
'ELECTRON_DISABLE_SECURITY_WARNINGS': true
})
]
I was originally trying with DefinePlugin, like so:
plugins: [
new HtmlWebpackPlugin(),
new MiniCssExtractPlugin(),
new webpack.DefinePlugin({
'process.env.NODE_ENV': JSON.stringify('development'),
// disables electron warning about insecure content that only applies in dev scenario
'process.env.ELECTRON_DISABLE_SECURITY_WARNINGS': true
})
]
In both cases, the build succeeds, but the setting has no effect and I see the warnings in the JS console. What gives?
Using webpack 4 & electron 3.
webpack electron
asked Nov 25 '18 at 20:46
TomTom
2,57132338
add a comment |
In development, content for my electron app is served by webpack-dev-server, over localhost:8080. This triggers some noisy warnings in the JS console. I want to shut them off, because the production app won't actually be loading any content from external sources.
In main.js, I can do this:
process.env.ELECTRON_DISABLE_SECURITY_WARNINGS = true
That works great, but I don't like that this is hard-coded into the source code. I think stuff like this should be provided by the dev build process.
I've tried using webpack EnvironmentPlugin, but it doesn't have any effect.
Relevant snippet from webpack.dev.config.js
plugins: [
new HtmlWebpackPlugin(),
new MiniCssExtractPlugin(),
new webpack.EnvironmentPlugin({
'NODE_ENV': JSON.stringify('development'),
// disables electron warning about insecure content that only applies in dev scenario
'ELECTRON_DISABLE_SECURITY_WARNINGS': true
})
]
I was originally trying with DefinePlugin, like so:
plugins: [
new HtmlWebpackPlugin(),
new MiniCssExtractPlugin(),
new webpack.DefinePlugin({
'process.env.NODE_ENV': JSON.stringify('development'),
// disables electron warning about insecure content that only applies in dev scenario
'process.env.ELECTRON_DISABLE_SECURITY_WARNINGS': true
})
]
In both cases, the build succeeds, but the setting has no effect and I see the warnings in the JS console. What gives?
Using webpack 4 & electron 3.
webpack electron
asked Nov 25 '18 at 20:46
TomTom
2,57132338
add a comment |
In development, content for my electron app is served by webpack-dev-server, over localhost:8080. This triggers some noisy warnings in the JS console. I want to shut them off, because the production app won't actually be loading any content from external sources.
In main.js, I can do this:
process.env.ELECTRON_DISABLE_SECURITY_WARNINGS = true
That works great, but I don't like that this is hard-coded into the source code. I think stuff like this should be provided by the dev build process.
I've tried using webpack EnvironmentPlugin, but it doesn't have any effect.
Relevant snippet from webpack.dev.config.js
plugins: [
new HtmlWebpackPlugin(),
new MiniCssExtractPlugin(),
new webpack.EnvironmentPlugin({
'NODE_ENV': JSON.stringify('development'),
// disables electron warning about insecure content that only applies in dev scenario
'ELECTRON_DISABLE_SECURITY_WARNINGS': true
})
]
I was originally trying with DefinePlugin, like so:
plugins: [
new HtmlWebpackPlugin(),
new MiniCssExtractPlugin(),
new webpack.DefinePlugin({
'process.env.NODE_ENV': JSON.stringify('development'),
// disables electron warning about insecure content that only applies in dev scenario
'process.env.ELECTRON_DISABLE_SECURITY_WARNINGS': true
})
]
In both cases, the build succeeds, but the setting has no effect and I see the warnings in the JS console. What gives?
Using webpack 4 & electron 3.
webpack electron
asked Nov 25 '18 at 20:46
TomTom
2,57132338
In development, content for my electron app is served by webpack-dev-server, over localhost:8080. This triggers some noisy warnings in the JS console. I want to shut them off, because the production app won't actually be loading any content from external sources.
In main.js, I can do this:
process.env.ELECTRON_DISABLE_SECURITY_WARNINGS = true
That works great, but I don't like that this is hard-coded into the source code. I think stuff like this should be provided by the dev build process.
I've tried using webpack EnvironmentPlugin, but it doesn't have any effect.
Relevant snippet from webpack.dev.config.js
plugins: [
new HtmlWebpackPlugin(),
new MiniCssExtractPlugin(),
new webpack.EnvironmentPlugin({
'NODE_ENV': JSON.stringify('development'),
// disables electron warning about insecure content that only applies in dev scenario
'ELECTRON_DISABLE_SECURITY_WARNINGS': true
})
]
I was originally trying with DefinePlugin, like so:
plugins: [
new HtmlWebpackPlugin(),
new MiniCssExtractPlugin(),
new webpack.DefinePlugin({
'process.env.NODE_ENV': JSON.stringify('development'),
// disables electron warning about insecure content that only applies in dev scenario
'process.env.ELECTRON_DISABLE_SECURITY_WARNINGS': true
})
]
In both cases, the build succeeds, but the setting has no effect and I see the warnings in the JS console. What gives?
Using webpack 4 & electron 3.
webpack electron
webpack electron
asked Nov 25 '18 at 20:46
TomTom
2,57132338
asked Nov 25 '18 at 20:46
TomTom
2,57132338
asked Nov 25 '18 at 20:46
TomTom
2,57132338
asked Nov 25 '18 at 20:46
TomTom
2,57132338
asked Nov 25 '18 at 20:46
TomTom
2,57132338
2,57132338
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53471796%2fhow-to-disable-electron-security-warnings-using-webpack-environmentplugin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53471796%2fhow-to-disable-electron-security-warnings-using-webpack-environmentplugin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
