Console shows "Electron Security Warning" after the last update
See original GitHub issueIs anyone else seeing this?
How to reproduce this problem:
- Create a new electron-vue project
- Run it (
yarn run dev
) - You should see the “Electron Security Warning” in the console right away
Tell me about your development environment.
- Node version: 9.4.0
- NPM version: 5.6.0
- vue-cli version: 2.5.13
- Operating System: Win10
Issue Analytics
- State:
- Created 6 years ago
- Reactions:5
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Why do I see an "Electron Security Warning" after updating my ...
They only show up when the binary's name is Electron, indicating that a developer is currently looking at the console.
Read more >Security | Electron
Security warnings and recommendations are printed to the developer console. They only show up when the binary's name is Electron, indicating that a...
Read more >Electron Security Warning 'Insecure Content-Security-Policy'
Solution: Electron Security Warning (Insecure Content-Security-Policy) This renderer process has either no Content Security Policy set or a policy with ...
Read more >Security, Native Capabilities, and Your Responsibility | Electron
From Electron 2.0 on, developers will see warnings and recommendations printed to the developer console. They only show up when the binary's name...
Read more >November 2022 (version 1.74) - Visual Studio Code
If you notice any issues, you can let us know by creating an issue in the vscode repository and you can opt out...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@robin7331 you are right, it just hides all those scary warnings, but there’s still no explanation on how to fix those problems.
Here’s a follow up thread: https://github.com/electron/electron/issues/12049
Not sure if disabling the warning solves the actual issue. Why is this closed?