You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-27Lines changed: 4 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,10 +5,10 @@ The aim of this repository is to help setting up Visual Studio Code for developm
5
5
Visual Studio Code comes with Electron support and Typescript support out of the box, but bringing the two together requires some advanced knowledge of the available configuration options. The repository contains a README with step by step instructions and an example project to demonstrate how Visual Studio Code, Node, Electron and Typescript must be configured to work together.
6
6
7
7
The latest example project has been created and tested on Linux with
8
-
- Node v16.6.1
9
-
- Electron v13.1.8
10
-
- Typescript v4.3.5
11
-
- Visual Studio Code v1.59.0
8
+
- Node v16.8.0
9
+
- Electron v14.0.0
10
+
- Typescript v4.4.2
11
+
- Visual Studio Code v1.60.0
12
12
13
13
## Install application
14
14
```sh
@@ -41,29 +41,6 @@ npm start
41
41
- In the Electron example app, click the "Turn page red" button.
42
42
- The breakpoint in `renderer.ts` will be hit.
43
43
44
-
---
45
-
**Troubleshooting**
46
-
47
-
If you are using Visual Studio Code v1.56.x or older, you may find that the breakpoint in `renderer.ts` is not hit and marked as unbound instead:
This is because of a [bug](https://github.com/microsoft/vscode/issues/123420) in the internal JavaScript debugger. As a workaround, you can either update to the latest version of Visual Studio Code, or use the "Debugger for Chrome" extension:
52
-
- Install the "Debugger for Chrome" extension v4.12.12
53
-
54
-

55
-
- In `.vscode/launch.json`, change the renderer configuration type from `pwa-chrome` to `chrome`
56
-
- Change settings to prevent the "Debugger for Chrome" extension from using the internal Javascript debugger:
When you run the "Electron: All" configuration the next time, the breakpoint should be hit.
64
-
65
-
66
-
67
44
## How does it work?
68
45
69
46
Electron has two kinds of processes: a main process and renderer processes (one for each tab). They need different launch configurations, which are shown below. The code snippets are taken from the [launch configuration](.vscode/launch.json).
0 commit comments