- DEBUGGING ELECTORN IN VS CODE FOR MAC HOW TO
- DEBUGGING ELECTORN IN VS CODE FOR MAC FREE
- DEBUGGING ELECTORN IN VS CODE FOR MAC WINDOWS
DEBUGGING ELECTORN IN VS CODE FOR MAC HOW TO
This answer on StackOverflow describes how to create a custom Chrome app only with a text editor.
It's a kind of shortcut that will simply start Chrome with command line arguments. In both cases you end up with a new Chrome app that you can add to the dock to replace the original app. I've found two options on the Internet that I will include in the following.
DEBUGGING ELECTORN IN VS CODE FOR MAC WINDOWS
On Windows it's straightforward as you just have to right-click on the Chrome shortcut, go to properties and append the above command line argument to the target field like this: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe -remote-debugging-port=9222 - "%1" Start Chrome Always with Remote DebuggingĪnother more convenient option is to start Chrome always with remote debugging enabled. I guess that's also the reason I was not able to attach the VSCode debugger to my running React app. In my case, it re-used the existing Chrome window and didn't enable remote debugging. Then, when React wants to launch a new window, Chrome internally checks if it can use an existing window or if it has to create a new window. My assumption is that you enable remote debugging on process level and if you already started Chrome by clicking on the icon, remote debugging is not enabled by default. If Chrome is already running on your system, this React start script will not create a new window but will create a new tab on your existing Chrome window. You have to close Chrome completely before running this script. For example, Chrome is google chrome on macOS, google-chrome on Linux and chrome on Windows. The name of the browser depends on the operating system. However, the advanced configuration allows us to change the browser and how it is launched by setting two environment variables BROWSER and BROWSER_ARGS:Įnter fullscreen mode Exit fullscreen mode Unfortunately, the default React start script launches a browser without remote debugging (maybe for safety reasons?). When you click debug on VSCode it does exactly that: It starts a new browser window with this command line argument. For example, Chrome has to be started with the flag -remote-debugging-port=9222. In order to debug JS apps, the browser has to be started with remote debugging enabled. However, I didn't want to accept that issue any longer and decided to figure out what I'm missing.
And that's the reason I didn't use the debugger in the first place. So effectively you end up with two instances of the same app. Unfortunately, launching a new browser means you have to navigate to the page you actually want to debug and you lose all your state (e.g. Until now, I was only using the first option of launching a new window because I wasn't able to get the second option working. On the other hand, VSCode offers two debugging options for JS apps: Launching the debugger with a new browser window or attaching the debugger to the already running app on a certain browser window/tab. If I need to check the value of a certain variable, I log it to the console and check the output on Chrome Dev Tools. A new Chrome tab is opened by React and I just keep this tab open forever. Usually, the React app is started with npm run start/yarn start (react-scripts start) and it runs on localhost:3000 and hot reloads when making file changes. It's not that I don't like debuggers, debugging JS is just not as convenient as it is in other programming languages. Only if it's really tricky, I use the VSCode debugger. When developing a React app (or any JavaScript app), I heavily use console.log() for debugging purposes if something is not running as expected. Here's a link to Visual Studio Code's open source repository on GitHub.Īccording to the StackShare community, Visual Studio Code has a broader approval, being mentioned in 1135 company stacks & 2385 developers stacks compared to JetBrains Rider, which is listed in 6 company stacks and 5 developer stacks.UPDATE: I released a npm package create-chrome-debugger that creates a Chrome Debugger shortcut to start Chrome in Remote Debugging Mode. Visual Studio Code is an open source tool with 79.4K GitHub stars and 11.1K GitHub forks. JetBrains Rider can be classified as a tool in the "Integrated Development Environment" category, while Visual Studio Code is grouped under "Text Editor".
DEBUGGING ELECTORN IN VS CODE FOR MAC FREE
Code is free and available on your favorite platform - Linux, Mac OSX, and Windows. Build and debug modern web and cloud applications. NET desktop applications, services and libraries, Unity games, Xamarin apps, ASP.NET and Visual Studio Code: Build and debug modern web and cloud applications, by Microsoft. This lets you develop a wide array of applications including.
NET IDE based on the IntelliJ platform and ReSharper. JetBrains Rider vs Visual Studio Code: What are the differences?
0 kommentar(er)
