![]() Var child = proc.spawn(electron, (2), ) īut this one inherits stdio and therefore the outputs should go to the same channel. I'm not sure how to debug the main process in intellij, tricky because electron-webpack dev runs webpack scripts using nodejs as interpreter but then it spawns electron. The problem might be related to the fact that 'cli.js' spawns a child process: #!/usr/bin/env node Debugging the running of electron-webpack dev as an npm script will only let you debug inside of your webpack configuration scripts though. When I directly start the Electron application from a Windows console window then this console window shows all the outputs. I can’t find any newer solution/guide online that doesnt reference that old article, and primarily just want WebStorm to properly recognize the Electron types/functions/etc. 2022 debug typesript with intellij questions debugging electron/vue/typescript. These instruction are applicable for the code base of electron-react-boilerplate on GitHub. The main difference is that in the run configuration I have to use a node parameter 'C:\Users\Username\AppData\Roaming\npm\node_modules\electron-prebuilt\cli.js' to get the right Electron entry point. Debug hardhat project using intellij - Ethereum Stack Exchange Debug code. (default is 10s)įurther references in the world of bleeding edge software.In a "normal" node application in Webstorm (Windows 7) I can use console.log to write to the console window of Webstorm.Īs soon as I use Electron to create a desktop app the console outputs are no longer shown in the Webstorm console window although I use the same node command 'C:\Program Files\nodejs\node.exe'. This command will prompt you to configure some fields in your package.json. mkdir my-electron-app & cd my-electron-app. ![]() I tried a lot of different ways to debug the renderer thread from within WebStorm to no avail. Unfortunately, WebStorm feels the same way. Start by creating a folder and initializing an npm package within it with npm init. I have an electron app that uses vue and is run with the vue-cli. This can be phonegap, phonegap.cmd, cordova, or cordova.cmd, depending on your operating system and the selected framework. Electron apps are scaffolded using npm, with the package.json file as an entry point. With WebStorm, you can debug all kinds of applications written in JavaScript, TypeScript, or Dart: Node.js, React Native and Electron applications and. I set it to 20 seconds, but you are free to lower it if your PC is fast enough. Check the location of the executable file or specify the path to it if WebStorm has not detected the executable automatically. You can append this flag here, and then configure your text editor to remotely connect localhost:5757. This is possible with the -remote-debugging-port5757 flag (port 5757 is just an example). quasar) is 'accessible' (green dot in ChromeDevTools). What you need to configure is a way to enable some sort of remote debugging. Since we're waiting for a child process to finish spawning, it may take longer than 10 seconds to launch and then attach. Just to share this info in here: I found that when I attach a NodeJS debugger (using Webstorm or the ChromeDevTools for example) I can see the electron-main.js file (in. This is the port of the child process, spawned by dev-runner.js "timeout": 20000 Maybe it’s only possible to debug the main process and you can’t stop the debugger in a component or in a router.js file for example. ![]() And trying to set up VS Code debug configurations like this "` I’m just creating a simple SPA, but for Electrons apps you might try: quasar dev -m electron -remote-debugging-port 9222. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |