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
+8-8Lines changed: 8 additions & 8 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 v18.3.0
9
-
- Electron v19.0.4
10
-
- Typescript v4.7.3
11
-
- Visual Studio Code v1.68.0
8
+
- Node v18.6.0
9
+
- Electron v19.0.8
10
+
- Typescript v4.7.4
11
+
- Visual Studio Code v1.69.1
12
12
13
13
## Install application
14
14
```sh
@@ -48,14 +48,14 @@ npm start
48
48
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).
49
49
50
50
### Main process
51
-
The main process can be debugged with the pwa-node debugger, that ships with Visual Studio Code.
51
+
The main process can be debugged with the node debugger, that ships with Visual Studio Code.
52
52
53
53
The launch configuration looks like this:
54
54
55
55
```jsonc
56
56
{
57
57
"name":"Electron: Main",
58
-
"type":"pwa-node", //use the node debugger that comes with VS Code
58
+
"type":"node",//use the node debugger that comes with VS Code
@@ -77,12 +77,12 @@ In the `sourceMaps` and `resolveSourceMapLocations` sections, we enable the crea
77
77
In the `runtimeArgs` section, we open a port for the renderer process. There is a counterpart defined in the renderer process configuration as shown below.
78
78
79
79
### Renderer process
80
-
A renderer process can be debugged with the pwa-chrome debugger, that ships with Visual Studio Code.
80
+
A renderer process can be debugged with the chrome debugger, that ships with Visual Studio Code.
81
81
82
82
```jsonc
83
83
{
84
84
"name":"Electron: Renderer",
85
-
"type":"pwa-chrome", //use the Chrome debugger that comes with VS Code
85
+
"type":"chrome",//use the Chrome debugger that comes with VS Code
86
86
"request":"attach",
87
87
"port":9223, //use debug port opened in Electron: Main configuration
0 commit comments